Methods and Apparatuses Supporting Multiple Positioning Protocol Versions in Wireless Communication Networks

ABSTRACT

Methods and apparatuses are provided for supporting multiple positioning protocol versions within wireless communication networks.

RELATED APPLICATIONS

This patent application claims benefit of and priority to U.S.Provisional Patent Application 61/029,288, filed Feb. 15, 2008, andtitled “Positioning Protocol for CDMA, UMB and other Wireless Systems”,and which is incorporated in its entirety by reference herein.

This patent application claims benefit of and priority to U.S.Provisional Patent Application 61/091,692, filed Aug. 25, 2008, andtitled “MS Information and BS Capabilities for IS-801-B”, and which isincorporated in its entirety by reference herein.

This patent application claims benefit of and priority to U.S.Provisional Patent Application 61/091,699, filed Aug. 25, 2008, andtitled “Location Response, Reject and Cancellation Request/Response”,and which is incorporated in its entirety by reference herein.

BACKGROUND

1. Field

The subject matter disclosed herein relates to wireless communicationnetworks and devices and more particularly to methods and apparatusesfor supporting multiple positioning protocol versions within wirelesscommunication networks.

2. Information

Position determination processes may be used to estimate or otherwisedetermine a location of a device associated with a wirelesscommunication network. In a particular example, a position determinationprocess may be implemented to estimate the location coordinates for amobile device such as a cellular telephone or other like mobile station.There are a variety of techniques available to support positiondetermination processes. For example, the Global Positioning System(GPS) and/or other like systems may be used to estimate the location ofa mobile station. In the context of a wireless communication network,certain position determination processes may require that informationand/or processing tasks be shared and/or distributed between and/oramong multiple devices. For example, in certain instances a mobilestation may be assisted in some manner by one or more other devices aspart of a position determination process. As a result, there is often aneed for such devices to communicate in some manner, for example, viaone or more position determination communication sessions over awireless link. Thus, one or more positioning protocols may be developedto enable such position determination communication sessions that may beused to support position determination processes.

SUMMARY

In accordance with certain aspects of the present description, robustand efficient version negotiation techniques are presented which maysupport multiple compatible and/or incompatible protocol versions,and/or which may allow for certain protocol versions to be “skippedover” or otherwise not supported.

In accordance with certain exemplary aspects, methods (and/or specificapparatuses) may be implemented which include, with a first device,determining at least one of a plurality of positioning protocol versionsthat the first device may be operatively enabled to support in additionto a first positioning protocol version. For example, the plurality ofpositioning protocol versions may include at least a second positioningprotocol version and a third positioning protocol version. The methodmay include accessing at least one indication signal identifying atleast one of the plurality of positioning protocol versions and/or thefirst positioning protocol version that a second device may beoperatively enabled to support, and in response to the indicationsignal, selectively transmitting at least one capability signal to thesecond device. Here, for example, if it may be determined that both thefirst and second devices are operatively enabled to support the thirdpositioning protocol version, then the capability signal initiates aposition determination communication session using the third positioningprotocol version. If it may be determined that the first device may benot operatively enabled to support the second positioning protocolversion but the second device may be operatively enabled to support thesecond positioning protocol version, then the capability signalinitiates the position determination communication session using thefirst positioning protocol version. Otherwise, if it may be determinedthat the first and second devices are operatively enabled to support thesecond positioning protocol version, then the capability signalinitiates the position determination communication session using thesecond positioning protocol version and the capability signal may betransmitted as needed to be in compliance with the second positioningprotocol version.

By of example, but not limitation, the indication signal received fromthe second device may include at least one transport message, which mayinclude a Position Determination Data Message (PDDM) for eachpositioning protocol version that the second device supports. Here, forexample, a first PDDM may be provided which includes a message typefield associated with the first positioning protocol version. In certainimplementations, a first PDDM may also include a Request “first device”Capabilities request element and/or a Provide “second device”Capabilities response element. If the second device supports the secondpositioning protocol version, then a second PDDM may be provided whichincludes a message type field associated with the second positioningprotocol version along with a Request Extended “first device”Capabilities request element, and an unsolicited Provide Extended“second device” Capabilities response element. If the second devicesupports the third positioning protocol version, for example, then athird PDDM may be provided which may include a message type fieldassociated with the third positioning protocol version along with aRequest Advanced “first device” Capabilities request element and anunsolicited Provide Advanced “second device” Capabilities responseelement.

In certain implementations, message length information may be providedwithin a transport message to identify portion(s) of the transportmessage associated with the second and/or third PDDMs. In certainimplementations, the third PDDM may include a payload that may beencoded, at least in part, using an extensible syntax language.

In accordance with certain other exemplary aspects, methods (and/orspecific apparatuses) may be implemented which include, with a firstdevice, determining at least one of a plurality of positioning protocolversions that the first device may be operatively enabled to support inaddition to a first positioning protocol version, and transmitting anindication signal to a second device, e.g., a PDDM for each positioningprotocol version that the first device supports.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic block diagram illustrating an example wirelesscommunication network environment within which at least two devices maybe enabled to communicate with one another and initiate and/or otherwisesupport a position determination process, in accordance with animplementation.

FIG. 2 is a schematic block diagram illustrating certain examplefeatures of a device that may be enabled to initiate and/or otherwisesupport a position determination process in accordance with animplementation.

FIG. 3A is a flow-diagram illustrating an exemplary method that may beimplemented in one or more devices to initiate and/or otherwise supporta position determination process in accordance with an implementation.

FIG. 3B is a flow-diagram illustrating an exemplary method that may beimplemented in one or more devices to initiate and/or otherwise supporta position determination process in accordance with an implementation.

FIG. 4 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 5 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 6 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 7 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 8 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 9 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 10 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 11 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 12 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 13 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 14 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 15 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 16 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 17 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 18 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 19 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 20 is a diagram illustrating example messages that may be providedin an indication signal(s) to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 21 is a diagram illustrating an example transport message that maybe provided in a capability signal(s) to initiate and/or otherwisesupport a position determination process using one or more positioningprotocol versions, in accordance with certain implementations.

FIG. 22 is a flow-diagram illustrating an exemplary method that may beimplemented in one or more devices to process a transport message, forexample, as in FIG. 21, to initiate and/or otherwise support a positiondetermination process in accordance with an implementation.

FIG. 23 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 24 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

FIG. 25 is a flow diagram illustrating an exemplary message exchangebetween two devices enabled to initiate and/or otherwise support aposition determination process using one or more positioning protocolversions, in accordance with certain implementations.

DETAILED DESCRIPTION

Non-limiting and non-exhaustive aspects are described with reference tothe following figures, wherein like reference numerals refer to likeparts throughout the various figures unless otherwise specified.

Position determination processes may be used to estimate or otherwisedetermine a location of a device and in particular examples the locationof a mobile device such as a mobile station. There are a variety oftechniques available to support position determination processes. In thecontext of a wireless communication network, certain positiondetermination processes may require that information and/or processingtasks be distributed between and/or among multiple devices. For example,in certain instances a mobile station may be assisted in some manner byone or more other devices as part of a position determination process.As a result, there may be a desire for such devices to communicate insome manner, for example, via one or more position determinationcommunication sessions over a wireless link. One or more positioningprotocols may, therefore, be developed to enable such positiondetermination communication sessions that may be used to supportposition determination processes.

By way of example but not limitation, positioning protocols have beendeveloped and standardized for use in CDMA2000 1X and High Rate PacketData (HRPD) wireless communication networks. One example positioningprotocol is often referred to by its standardization identity as“IS-801” in the Telecommunications Industry Association (TIA) publishedstandards (or “C.S0022” in Third-Generation Partnership Project 2(3GPP2) published standards). Currently, there are two versions of thisexample positioning protocol. The first version is the initial versionIS-801 version 1 (or C.S0022-0 version 3.0), which will simply bereferred to herein as IS-801-1. The second version is IS-801 version A(or C.S0022-A version 1.0), which will simply be referred to herein asIS-801-A.

In the sections that follow, reference will be made to future versions(e.g., similar and/or other protocols, extensions, revisions, etc.) ofexample positioning protocols and for the sake of brevity and continuitythese may be referred to as “IS-801-B”, “IS-801-C”, and “IS-801-D”, eventhough such versions may or may not at the time of this writing be knownor even planned. It is expected, however, that some form of IS-801-Bwill soon be finalized and will be identified in some manner by TIA and3GPP2 (e.g., perhaps as IS-801 version B (or C.S0022-B version 1.0),and/or other like identifiers).

Accordingly, certain example implementations of the methods andapparatuses provided herein may be enabled to support one or morestandardized positioning protocols, and/or the like. Other exampleimplementations of the methods and apparatuses provided herein may beenabled to provide capabilities and features that, while not necessarilyincluded in a standardized positioning protocol, may nonetheless bebeneficial if implemented in certain devices that may be or may not becompliant with such standardized positioning protocols and/or the like.Thus, in certain example implementations, the methods and apparatusesprovided herein may be commercially and/or otherwise beneficiallyimplemented in devices to allow such devices to comply in other wayswith one or more standardized and/or non-standardized positioningprotocols.

With regard to IS-801-1 and IS-801-A, these two example positioningprotocol versions are not compatible with one another (e.g., differentmessage sets, etc.) and as such the devices (e.g., a mobile station,base station/PDE) need to decide which version will be used prior toinitiating a position determination communication session. Thus, forexample, an IS-801-A negotiation sequence requires that an originatingdevice send separate messages, e.g., one associated with IS-801-A andone associated with IS-801-1, to a terminating device in a specificmanner. The terminating device sends an applicable response identifyingthe “highest” level version that both the terminating and originatingdevices are enabled to support. In addition to providing a message setthat is incompatible with the older IS-801-1 version, the versionnegotiation sequence implemented to support IS-801-A does not appear tobe adequately flexible and/or scalable enough to efficiently supportnewer protocol versions as they are developed.

In accordance with certain aspects of the present description, robustand efficient version negotiation techniques are presented which maysupport more than two protocol versions and which may allow for certainlevel versions to be skipped over or otherwise not supported.

Thus, for example, as described in greater detail below in certainimplementations a device that supports IS-801-B or later version maynegotiate to an earlier or “lower” level version such as IS-801-1,thereby effectively skipping over IS-801-A and/or other possiblyintervening level versions. As such, certain devices may be enabled tosupport all or just selected positioning protocol versions.Additionally, the exemplary techniques presented herein may beimplemented in a manner that allows for forward compatibility to futureversions.

Newer positioning protocol versions, such as IS-801-B, may be developedto make use of new technology. For example, certain methods andapparatuses provided herein may use IS-801-B messages to request/provideposition determination related information/services associated with newSPS (e.g., GNSS) resources such as future GPS resources, a SatelliteBased Augmentation System (SBAS) resource, a QZSS resource, a GLONASSresource, a Galileo resource, a Compass/BeiDou resource, and/or otherlike resources. Here, for example, an SPS resource may be associatedwith one or more SPS signals, one or more SPS signal bands, one or morespace vehicles (SVs), SBAS resources, and/or the like or combinationthereof. These messages, e.g., Position Determination Data Messages(PDDMs) and/or transport messages may be implemented to supportIS-801-B, as well as legacy and/or future versions. Further still,certain methods and apparatuses may be enabled to support locationpositioning processes in a variety of wireless communication networks,such as, e.g., an Ultra Mobile Broadband (UMB) network, a High RatePacket Data (HRPD) network, a CDMA2000 1X network, and/or the like.

In accordance with certain aspects of the present description variousmethods and apparatuses are provided which may be implemented in a firstdevice that may be enabled to communicate with a second device toinitiate a position determination process. By way of example but notlimitation, the first and/or second devices may include a mobilestation, a base station, a location server (e.g., a PositionDetermination Entity (PDE), Serving Mobile Location Center (SMLC),Gateway Mobile Location Center (GMLC), Standalone AGPS SMLC (SAS), SUPLLocation Platform (SLP), etc.), and/or the like. For example, in certainimplementations a mobile station and base station may be operativelyenabled to communicate within a CDMA wireless communication network,and/or other applicable type of wireless communication network.

The methods and apparatuses may be implemented in such devices to allowthe devices to initiate and/or otherwise establish a positiondetermination communication session associated with a positiondetermination process. A position determination communication sessionmay, for example, utilize a specific positioning protocol depending onthe capabilities of the devices involved. Accordingly, the methods andapparatuses may be enabled to allow for positioning protocol versionnegotiation. By way of example but not limitation, a mobile station anda base station may be enabled to support and/or otherwise perform aThird-Generation Partnership Project 2 (3GPP2) compliant positiondetermination process.

The methods and apparatuses may be implemented to allow for differentpositioning protocol versions within a network. In certain exampleimplementations, all or portions of a network may be enabled to supporta plurality of positioning protocol versions including a firstpositioning protocol version, and at least a second positioning protocolversion and a third positioning protocol version. Here, for example, thesecond and third positioning protocol versions may include different andpossibly subsequently developed/implemented revisions of the firstpositioning protocol version.

By way of example but not limitation, a first positioning protocolversion may be compliant with IS-801-1, a second positioning protocolversion may be compliant with IS-801-A, and a third positioning protocolversion may be compliant with IS-801-B. Similarly, a fourth, or laterpositioning protocol version may be compliant with a future version ofsuch standards and/or the like. The methods and apparatuses may, forexample, be enabled to allow for or otherwise support backward and/orforward compatibility between various positioning protocol versionswithin a network.

For example, certain methods and apparatuses may implement a positioningprotocol version initiation sequence (e.g., supportive of versiondiscovery and/or negotiation) that is compatible with a plurality ofdifferent versions of a positioning protocols, and/or correspondingservices and/or messages. With regard to IS-801-A (e.g., which may beconsidered to be a second positioning protocol version in the examplesherein), certain methods and apparatuses may implement a positioningprotocol version negotiation process that allows for backwardcompatibility to a second positioning protocol version initiationsequence as may be applicable to initiate a position determinationcommunication session between two IS-801-A compliant devices. Forexample, a second positioning protocol version initiation sequence mayintroduce different messaging requirements which may or may not becompatible in some manner with one or more positioning protocolversions.

In accordance with certain aspects, therefore, example methods andapparatuses may be implemented that allow for devices that may not becompatible with each preceding and/or successive positioning protocolversions. For example, a device may support a first positioning protocolversion and a third and/or fourth, and/or later positioning protocolversion, while not supporting a second positioning protocol version.

Such capability may be beneficial for example, to manufactures ofdevices, circuits, and/or software that choose not to support one ormore positioning protocol versions. Thus, for example, a manufacturer ofchipsets (e.g., a specific apparatus, processing units, implementableinstructions, etc.) for certain devices (e.g., mobile stations, basestations, etc.) may choose to reduce costs and/or time duringdevelopment and/or manufacturing by supporting only a subset of thepositioning protocol versions for a given network. Here, for example, achipset and/or devices may support an initial (e.g., first) positioningprotocol version and perhaps the latest and/or certain applicable (e.g.,popular, efficient, etc.) positioning protocol version(s), rather thansupporting all of the positioning protocol versions. With this in mind,the methods and apparatuses may be implemented in certainimplementations to support various positioning protocol versions and/orcertain initiation messaging sequences associated therewith.

As described in greater detail in subsequent sections, in certainexample implementations, a position determination communication sessionthat uses a third positioning protocol version may allow the firstand/or second devices to request and/or provide information associatedwith various Global Navigation Satellite Service (GNSS). A thirdpositioning protocol version may allow the first and/or second devicesto operate with the support of an Ultra Mobile Broadband (UMB) network,a High Rate Packet Data (HRPD) network, a CDMA2000 1X network, GSM, LTE,and/or the like. In certain example implementations, a positiondetermination communication session that uses a third positioningprotocol version may allow the first and/or second devices to rejectand/or cancel position determination related processes associated with aGNSS, a UMB network, a HRPD network, a CDMA2000 1X network, and/or thelike.

With this introduction in mind, methods and apparatuses may beimplemented in a first device that enable the first device to determinewhich of a plurality of positioning protocol versions the first devicemay be operatively enabled to support in addition to a first positioningprotocol version. Here, for example, the plurality of positioningprotocol versions include at least a second positioning protocolversion, and a third positioning protocol version. The first device mayalso be enabled to access at least one indication signal identifyingwhich of the plurality of positioning protocol versions in addition tothe first positioning protocol version that a second device may beoperatively enabled to support. For example, the indication signal maybe received by the first device from the second device, and/or mayalready be known (e.g., stored in memory within the first device).

In response to the indication signal, for example, the first device maybe enabled to selectively transmit at least one capability signal to thesecond device. If both the first and second devices are enabled tosupport the third positioning protocol version then the capabilitysignal may initiate a position determination communication session usingthe third positioning protocol version. If it is determined that atleast one of the first or second devices is not enabled to support thesecond positioning protocol version then the capability signal mayinitiate a position determination communication session using the firstpositioning protocol version. If it is determined that the first andsecond devices are enabled to support the second positioning protocolversion, then the capability signal may initiate a positiondetermination communication session using the second positioningprotocol version and may be, for example, transmitted in compliance witha second positioning protocol version initiation sequence.

In certain example implementations, as described in greater detailbelow, the indication signal may include at least one transport messageincluding a Position Determination Data Message (PDDM) for eachpositioning protocol version that the second device may be enabled tosupport. A PDDM may, for example, include one or more elements ormessages, some of which may have been solicited and some of which mayhave been unsolicited. For example, a “request” element or message mayelicit a solicited “provide” element or message, while an unsolicited“provide” element or message may be sent without having been requested.

By way of further general example, a first PDDM sent by a second deviceto a first device may be provided which includes a message type field orthe like that may be associated with a first positioning protocolversion. Here, for example, such first PDDM may include a Request “firstdevice” Capabilities request element and/or an unsolicited Provide“second device” Capabilities response element. If the second devicesupports a second positioning protocol version, for example, then asecond PDDM may be sent from the second device to the first device andmay include a message type field (or the like) associated with thesecond positioning protocol version. In certain examples, a second PDDMmay include a Request Extended “first device” Capabilities requestelement, and/or an unsolicited Provide Extended “second device”Capabilities response element. If the second device supports a thirdpositioning protocol version, for example, then a third PDDM may be sentfrom the second device to the first device and may include a messagetype field or the like that is associated with the third positioningprotocol version. In certain examples, a third PDDM may include aRequest Advanced “first device” Capabilities request element and/or anunsolicited Provide Advanced “second device” Capabilities responseelement.

Thus, for example, if the second device includes a mobile station (MS)and the first device includes a base station (BS) then a RequestAdvanced “first device” Capabilities request element may include aRequest Advanced BS Capabilities request element and an unsolicitedProvide Advanced “second device” Capabilities response element mayinclude an unsolicited Provide Advanced MS Capabilities responseelement.

Conversely, for example, if the second device includes a base station(BS) and the first device includes a mobile station (MS) then a RequestAdvanced “first device” Capabilities request element may include aRequest Advanced MS Capabilities request element and an unsolicitedProvide Advanced “second device” Capabilities response element mayinclude an unsolicited Provide Advanced BS Capabilities responseelement.

In certain example implementations, as described in greater detail insubsequent paragraphs, a transport message may include message lengthinformation that identifies a portion(s) of the transport messageassociated with at least one of the second PDDM and/or the third PDDM.One or more of the PDDMs and/or response elements may, for example,include a revision level indicator associated with one of either thefirst, second, or third positioning protocol versions.

In accordance with certain other aspects, various methods andapparatuses may be implemented in a first device to provide (e.g.,originate) an indication signal to second device. Here, for example, afirst device may be enabled to determine at least one of a plurality ofpositioning protocol versions the first device may be operativelyenabled to support in addition to a first positioning protocol version.Again, for example, the plurality of positioning protocol versions mayinclude at least a second positioning protocol version and a thirdpositioning protocol version.

The first device may also be enabled to transmit an indication signal toa second device. An indication signal may include a PDDM for eachpositioning protocol version that the first device supports. Thus, forexample, a first PDDM may be provided which includes a message typefield or the like that may be associated with the first positioningprotocol version. If the first device supports the second positioningprotocol version then a second PDDM may be provided which includes amessage type field or the like that may be associated with the secondpositioning protocol version. The second PDDM may, for example, includea Request Extended “second device” Capabilities request element and/oran unsolicited Provide Extended “first device” Capabilities responseelement. If the first device supports the third positioning protocolversion then a third PDDM may be provided which includes a message typefield or the like that is associated with the third positioning protocolversion. The third PDDM may, for example, include a Request Advanced“second device” Capabilities request element and/or an unsolicitedProvide Advanced “first device” Capabilities response element.

In certain implementations, an indication signal may include at leastone transport message that is transmitted within a Data Burst Message,an IP Packet, or the like. Thus, in certain implementations, a pluralityof PDDMs may be concatenated or otherwise arranged within a transportmessage. As such, for example, message length information may beincluded within the transport message that identifies or otherwisespecifies portions of the transport message associated with each PDDMwithin the transport message.

Attention is now drawn to FIG. 1, which is a schematic block diagramillustrating an example wireless communication network environment 100within which devices may be enabled to communicate with one another andinitiate and/or otherwise support a position determination process.

In this particular example, wireless communication network environment100 includes representative devices such as a mobile station (MS) 102,one or more base stations (BS) 104, one or more Satellite PositioningSystem(s) (SPS) 106, a network 108, and a location server 110. MS 102may be enabled to communicate with BS 104 over one or more wirelesscommunication links. One or more of MS 102, BS 104, or location server110 may be enabled to acquire SPS signals transmitted by varioustransmitting resources of SPS 106, and/or otherwise be enabled tosupport certain position determination processes associated withinformation available via SPS 106.

Although the representative devices in FIG. 1 are illustrated as beingcoupled by either wireless communication links or wired communicationlinks it should be understood that in certain example implementations atleast some the devices may be coupled together via one or more wired,fiber, and/or wireless communication link(s).

Unless specifically stated otherwise, as used herein, the term “locationserver” is intended to represent one or more devices and/or one or morespecific apparatuses therein that is/are enabled to support, at least inpart, such position determination processes. Thus, while illustrated asa separate device in the example shown in FIG. 1 that may communicatevia network 108 and/or a BS 104 with MS 102, it should be understoodthat in other implementations a “location server” may be enabled tocommunicate directly and/or indirectly with MS 102 using one or morewired and/or one or more wireless communication links. Hence, in certainexample implementations, a location server may take the form of and/orotherwise operatively comprise one or more wireless transmitters,receivers, transceivers, one or more base stations, various wired and/orwireless network resources, one or more computing devices enabled asspecific apparatuses, and/or other like computing and/or communicationdevices. With this in mind, where example references are made to a basestation (BS) or a BS 104, it should be understood that such BS and/or BS104 may comprise a “location server” as broadly defined herein.Accordingly, the terms base station (BS) and location server are usedinterchangeably. Further still, in messages requesting and/or providingBS capabilities, etc., it should be understood that such requestedinformation and/or provided information may be associated with locationserver capabilities, etc.

MS 102 and/or BS 104 may be enabled to provide functionality, forexample, through the use of various wireless communication networks suchas a wireless wide area network (WWAN), a wireless local area network(WLAN), a wireless personal area network (WPAN), and so on. The term“network” and “system” are often used interchangeably. A WWAN may be aCode Division Multiple Access (CDMA) network, a Time Division MultipleAccess (TDMA) network, a Frequency Division Multiple Access (FDMA)network, an Orthogonal Frequency Division Multiple Access (OFDMA)network, a Single-Carrier Frequency Division Multiple Access (SC-FDMA)network, and so on. A CDMA network may implement one or more radioaccess technologies (RATs) such as cdma2000, Wideband-CDMA (W-CDMA), andso on. CDMA2000 includes IS-95, IS-2000, and IS-856 standards. A TDMAnetwork may implement Global System for Communications (GSM), DigitalAdvanced Phone System (D-AMPS), or some other RAT. GSM and W-CDMA aredescribed in documents from a consortium named “3rd GenerationPartnership Project” (3GPP). CDMA2000 is described in documents from aconsortium named “3rd Generation Partnership Project 2” (3GPP2). 3GPPand 3GPP2 documents are publicly available. A WLAN may be an IEEE802.11x network, and a WPAN may be a Bluetooth network, an IEEE 802.15x,or some other type of network. The techniques may also be used for anycombination of WWAN, WLAN and/or WPAN. As mentioned earlier, thetechniques may be implemented for use with a UMB network, a HRPDnetwork, a CDMA2000 1X network, GSM, LTE, and/or the like.

SPS 106 may, for example, include one or more of the GPS, Galileo,GLONASS, NAVSTAR, SBAS, QZSS, Compass/BeiDou, and/or other like GNSS, asystem that uses satellites from a combination of these systems, or anySPS developed in the future, each referred to generally herein as a“Satellite Positioning System” (SPS).

Furthermore, the methods and apparatuses described herein may be usedwith position determination processes that utilize pseudolites or acombination of satellites and pseudolites. Pseudolites may includeground-based transmitters that broadcast a PN code or other ranging code(e.g., similar to a GPS or CDMA cellular signal) modulated on an L-band(or other frequency) carrier signal, which may be synchronized with SPStime. Each such transmitter may be assigned a unique PN code so as topermit identification by a remote receiver. Pseudolites may be used toaugment an SPS, for example, in situations where some SPS signals fromorbiting satellites might be unavailable, such as in tunnels, mines,buildings, urban canyons or other enclosed areas. Another implementationof pseudolites is known as radio-beacons. The term “satellite”, as usedherein, is intended to include pseudolites, equivalents of pseudolites,and possibly others. The term “SPS signals”, as used herein, is intendedto include SPS-like signals from pseudolites or equivalents ofpseudolites.

MS 102, in certain example implementations, may include a device such asa cellular or other wireless communication device, personalcommunication system (PCS) device, personal navigation device, a vehiclemountable navigation device, a tracking device, Personal InformationManager (PIM), Personal Digital Assistant (PDA), laptop or othersuitable device which may be capable of receiving wirelesscommunications.

The methodologies described herein may be implemented by various meansdepending upon the application. For example, these methodologies may beimplemented in hardware, firmware, software, or a combination thereof.For a hardware implementation, one or more processing units may beimplemented within one or more application specific integrated circuits(ASICs), digital signal processors (DSPs), digital signal processingdevices (DSPDs), programmable logic devices (PLDs), field programmablegate arrays (FPGAs), processors, controllers, micro-controllers,microprocessors, electronic devices, other electronic units designed toperform the functions described herein, or a combination thereof.

For a firmware and/or software implementation, certain methodologies maybe implemented with modules (e.g., procedures, functions, and so on)that perform the functions described herein. Any machine readable mediumtangibly embodying instructions may be used in implementing themethodologies described herein. For example, software codes may bestored in a memory of MS 102 and/or BS 104 and executed by a processingunit of the device. Memory may be implemented within a processing unitand/or external to the processing unit. As used herein the term “memory”refers to any type of long term, short term, volatile, nonvolatile, orother memory and is not to be limited to any particular type of memoryor number of memories, or type of media upon which memory is stored.

If implemented in software, functions that implement methodologies orportions thereof may be stored on and/or transmitted over as one or moreinstructions or code on a computer-readable medium. A computer-readablemedium may take the form of an article of manufacture. Acomputer-readable medium may include computer storage media and/orcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage media may be anyavailable media that may be accessed by a computer or like device. Byway of example but not limitation, a computer-readable medium maycomprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage,magnetic disk storage or other magnetic storage devices, or any othermedium that may be used to carry or store desired program code in theform of instructions or data structures and that may be accessed by acomputer.

“Instructions” as referred to herein relate to expressions whichrepresent one or more logical operations. For example, instructions maybe “machine-readable” by being interpretable by a machine for executingone or more operations on one or more data objects. However, this ismerely an example of instructions and claimed subject matter is notlimited in this respect. In another example, instructions as referred toherein may relate to encoded commands which are executable by aprocessing unit having a command set which includes the encodedcommands. Such an instruction may be encoded in the form of a machinelanguage understood by the processing unit. Again, these are merelyexamples of an instruction and claimed subject matter is not limited inthis respect.

Reference is now made to FIG. 2, which is a schematic block diagramillustrating certain example features of an apparatus 200 enabled toinitiate and/or otherwise support a position determination process.Apparatus 200 may, for example, be implemented in some form within MS102, BS 104, location server 110, and/or other like devices, asapplicable, to perform or otherwise support at least a portion of theexample techniques described herein.

Apparatus 200 may, for example, include one or more processing units202, memory 204, a transceiver 210, and (optionally) an SPS receiver240), which may be operatively coupled with one or more connections 206(e.g., buses, lines, fibers, links, etc.). In certain exampleimplementations, apparatus 200 may take the form of a chipset, and/orthe like.

Processing unit 202 may be implemented in hardware, software, or acombination of hardware and software. Thus, for example, processing unit202 may represent one or more circuits configurable to perform at leasta portion of a data computing procedure or process related to theoperation of device 200. By way of example but not limitation,processing unit 202 may include one or more processors, controllers,microprocessors, microcontrollers, application specific integratedcircuits, digital signal processors, programmable logic devices, fieldprogrammable gate arrays, and the like, or any combination thereof.

Memory 204 may represent any data storage mechanism. Memory 204 mayinclude, for example, a primary memory and/or a secondary memory.Primary memory may include, for example, a random access memory, readonly memory, etc. While illustrated in this example as being separatefrom processing unit 202, it should be understood that all or part of aprimary memory may be provided within or otherwise co-located/coupledwith processing unit 202. Secondary memory may include, for example, thesame or similar type of memory as primary memory and/or one or more datastorage devices or systems, such as, for example, a disk drive, anoptical disc drive, a tape drive, a solid state memory drive, etc.

In certain implementations, secondary memory may be operativelyreceptive of, or otherwise configurable to couple to, computer readablemedium 220. As such, in certain example implementations, the methodsand/or apparatuses presented herein may take the form in whole or partof a computer readable medium 220 that may include computerimplementable instructions 208 stored thereon, which if executed by atleast one processing unit 202 may be operatively enabled to perform allor portions of the example operations as described herein.

As illustrated in FIG. 2, memory 204 may also include instructionsand/or data associated with one or more positioning protocol versions230-1, 230-2, 230-3, . . . , 230-n. For example, positioning protocolversion 230-1 may include instructions and/or data associated with afirst positioning protocol version, positioning protocol version 230-2may include instructions and/or data associated with a secondpositioning protocol version, positioning protocol version 230-3 mayinclude instructions and/or data associated with a third positioningprotocol version, and positioning protocol version 230-n may includeinstructions and/or data associated with an “n^(th)” second positioningprotocol version.

Transceiver 210 may, for example, include a transmitter 212 enabled totransmit one or more signals over one or more wireless communicationlinks and a receiver 214 to receive one or more signals transmitted overone or more wireless communication links. In certain implementations,transceiver 210 may also support wired transmission and/or reception,e.g., when implemented within BS 104 and/or other like devices.

Attention is drawn next to FIGS. 3A and 3B, which are flow-diagramsillustrating some exemplary methods that may be implemented in apparatus200 and/or the like within a device to initiate and/or otherwise supporta position determination process.

In method 300-A, at block 302, it may be determined which positioningprotocol versions are supported by a first device. Here, for example, afirst device may take the form of MS 102, BS 104, and/or location server110 (see FIG. 1). By way of example but not limitation, method 300-A maydetermine which positioning protocol versions are supported by a firstdevice based on one or more positioning protocol versions 230-1, 230-2,230-3, . . . , 230-n (see FIG. 2). At block 304, one or more indicationsignals may be received and/or otherwise accessed to determine and/orotherwise identify which positioning protocol versions are supported bya second device. Here, for example, a second device may take the form ofMS 102, BS 104, and/or location server 110 (see FIG. 1) as applicable tocommunicate with the first device. By way of example but not limitation,method 300-B may determine which positioning protocol versions aresupported by a second device based on information within one or morePDDMs, and/or transport messages.

At block 306, at least one capability signal may be transmitted by thefirst device to the second device to initiate a position determinationcommunication session. In response to the indication signal, forexample, the first device may be enabled to selectively transmit atleast one capability signal to the second device. Here, for example, ifboth the first and second devices are determined to be enabled tosupport a third positioning protocol version, then a capability signalmay initiate a position determination communication session using thethird positioning protocol version. If it is determined that at leastone of the first or second devices is not enabled to support a secondpositioning protocol version then a capability signal may initiate aposition determination communication session using a first positioningprotocol version (e.g., a default or initial version). If it isdetermined that the first and second devices are enabled to support asecond positioning protocol version, then a capability signal mayinitiate a position determination communication session using the secondpositioning protocol version and may be, for example, transmitted incompliance with a second positioning protocol version initiationsequence.

In method 300-B, at block 310 it may be determined which positioningprotocol versions are supported by a first device (e.g., actually the“second” device in the example above in method 300-A). Here, forexample, a first device may take the form of MS 102, BS 104, and/orlocation server 110 (see FIG. 1). By way of example but not limitation,method 300-b may determine which positioning protocol versions aresupported by a first device based on one or more positioning protocolversions 230-1, 230-2, 230-3, . . . , 230-n (see FIG. 2).

At block 312, an indication signal(s) may be transmitted to a seconddevice (e.g., actually the “first” device in the example above in method300-A) via a transport message. By way of example, the indicationsignal(s) may include information within one or more PDDMs, and/ortransport messages that specify which positioning protocol version(s)are supported by the first device.

The above exemplary methods and apparatuses may, for example, be enabledto support positioning protocol version negotiation as illustrated inthe various examples as described below.

FIGS. 4-19 are flow diagrams illustrating various exemplary messageexchanges between two devices enabled to initiate and/or otherwisesupport a position determination process using one or more positioningprotocol versions. Here, by way of example but not limitation thedevices are illustrated as mobile stations and base stations, whichsupport at least one of at least three example positioning protocolversions. Here, for example, three positioning protocol versions mayinclude a first positioning protocol version (e.g., IS-801-1), a secondpositioning protocol version (e.g., IS-801-A), and/or a thirdpositioning protocol version (e.g., IS-801-B).

In these example flow diagrams, one of the devices is deemed as“originating” a position determination process and the other as“terminating” a position determination process. Also, in these exampleflow diagrams, various example messages are illustrated, which mayinclude one or more indication signals from an originating device to aterminating device, and one or more capability signals from aterminating device to an originating device. The one or more indicationsignals and/or one or more capability signals may, for example, includeone or more PDDMs within one or more transport messages. A PDDM mayinclude a PD_MSG_TYPE, and possibly one or more request elements and/orresponse elements. If two or more PDDMs are transmitted via a transportmessage, then in the example flow-diagrams they are listed above asingle arrow.

FIG. 4 shows an example version negotiation process 400, wherein anoriginating BS supports IS-801-1 and a terminating MS supports IS-801-1and IS-801-B. As shown at 402, the BS may transmit aPD_MSG_TYPE=“00000000” to the MS, which may serve as an indicationsignal specifying that the sender supports IS-801-1. In response at 404,the MS may transmit a PD_MSG_TYPE=“00000000” to the BS, which may serveas capability signal specifying that the sender supports IS-801-1 andwhich may initiate a position determination communication session, at406, using such positioning protocol version.

FIG. 5 shows an example version negotiation process 500, wherein anoriginating MS supports IS-801-1 and IS-801-B, and a terminating BSsupports IS-801-1. As shown at 502, the MS may transmitPD_MSG_TYPE=“00000000” and PD_MSG_TYPE=“00000010” to the BS, which mayserve as indication signal(s) specifying that the sender supportsIS-801-1 and IS-801-B, respectively. In response at 504, the BS maytransmit a PD_MSG_TYPE=“00000000” to the MS, which may serve ascapability signal specifying that the sender supports IS-801-1 and whichmay initiate a position determination communication session, at 506,using such positioning protocol version.

FIG. 6 shows an example version negotiation process 600, wherein anoriginating BS supports IS-801-1 and IS-801-A, and a terminating MSsupports IS-801-1, IS-801-A and IS-801-B. As shown at 602, the BS maytransmit PD_MSG_TYPE=“00000000” and PD_MSG_TYPE=“00000001” to the MS,which may serve as indication signal(s) specifying that the sendersupports IS-801-1 and IS-801-A, respectively. In response at 604, the MSmay transmit a PD_MSG_TYPE=“00000001” to the BS, which may serve ascapability signal specifying that the sender supports IS-801-A and whichmay initiate a position determination communication session, at 606,using such positioning protocol version. Here, for example, thecapability signal(s) may be transmitted in compliance with a specificinitiation sequence associated with IS-801-A.

FIG. 7 shows an example version negotiation process 700, wherein anoriginating MS supports IS-801-1 and (at least) IS-801-B, and aterminating BS supports IS-801-1 and IS-801-A. As shown at 702, the MSmay transmit PD_MSG_TYPE=“00000000” and at least PD_MSG_TYPE=“00000010”to the BS, which may serve as indication signal(s) specifying that thesender supports IS-801-1 and at least IS-801-B, respectively. Inresponse at 704, the BS may transmit a PD_MSG_TYPE=“00000000” to the MS,which may serve as capability signal specifying that the sender supportsIS-801-1 and which may initiate a position determination communicationsession, at 706, using such positioning protocol version.

FIG. 8 shows an example version negotiation process 800, wherein anoriginating BS supports IS-801-1 and IS-801-A, and a terminating MSsupports IS-801-1, IS-801-A and IS-801-B. As shown at 802, the BS maytransmit PD_MSG_TYPE=“00000000” to the MS and, at 804, the BS maytransmit PD_MSG_TYPE=“00000001” to the MS, which may serve as indicationsignal(s) specifying that the sender supports IS-801-1 and IS-801-A,respectively. Here, for example, indication signal(s) may be transmittedin compliance with a specific initiation sequence associated withIS-801-A. Also, here, in PD_MSG_TYPE=“00000000” a revisionBS_LS_REV=“00000001”, which may allow the MS to ignore thePD_MSG_TYPE=“00000000” PDDM at 802 and instead await thePD_MSG_TYPE=“00000001” PDDM at 804. Thus, in response at 806, the MS maytransmit a PD_MSG_TYPE=“00000001” to the BS, which may serve ascapability signal specifying that the sender supports IS-801-A and whichmay initiate a position determination communication session, at 808,using such positioning protocol version. Here also, for example, thecapability signal(s) may be transmitted in compliance with a specificinitiation sequence associated with IS-801-A.

FIG. 9 shows an example version negotiation process 900, wherein anoriginating MS supports IS-801-1 and (at least) IS-801-B, and aterminating BS supports IS-801-1 and IS-801-A. As shown at 902, the MSmay transmit PD_MSG_TYPE=“00000000” and PD_MSG_TYPE=“00000010” to theBS, which may serve as indication signal(s) specifying that the sendersupports IS-801-1 and at least IS-801-B, respectively. In response at904, the BS may transmit a PD_MSG_TYPE=“00000000” to the MS, which mayserve as capability signal specifying that the sender supports IS-801-1and which may initiate a position determination communication session,at 906, using such positioning protocol version.

FIG. 10 shows an example version negotiation process 1000, wherein anoriginating BS supports IS-801-1 and IS-801-A, and a terminating MSsupports IS-801-1 and IS-801-B. As shown at 1002, the BS may transmitPD_MSG_TYPE=“00000000” to the MS, and, at 1004, the BS may transmitPD_MSG_TYPE=“00000001” to the MS, which may serve as indicationsignal(s) specifying that the sender supports IS-801-1 and IS-801-A,respectively. Here, for example, the indication signal(s) may betransmitted in compliance with a specific initiation sequence associatedwith IS-801-A. Also, here, in PD_MSG_TYPE=“00000000” a revisionBS_LS_REV=“00000001”, which may allow the MS to ignore the subsequentPD_MSG_TYPE=“00000001” PDDM at 1004. Thus, in response at 1006, the MSmay transmit a PD_MSG_TYPE=“00000000” to the BS, which may serve ascapability signal specifying that the sender supports IS-801-1 and whichmay initiate a position determination communication session, at 1008,using such positioning protocol version. Here also, for example, thecapability signal(s) may be transmitted in compliance with a specificinitiation sequence associated with IS-801-1.

FIG. 11 shows an example version negotiation process 1100, wherein anoriginating MS supports IS-801-1 and IS-801-B, and a terminating BSsupports IS-801-1 and IS-801-A. As shown at 1102, the MS may transmitPD_MSG_TYPE=“00000000” and PD_MSG_TYPE=“00000010” to the BS, which mayserve as indication signal(s) specifying that the sender supportsIS-801-1 and IS-801-B, respectively. In response at 1104, the BS maytransmit a PD_MSG_TYPE=“00000000” to the MS, which may serve ascapability signal specifying that the sender supports IS-801-1 and whichmay initiate a position determination communication session, at 1106,using such positioning protocol version.

FIG. 12 shows an example version negotiation process 1200, wherein anoriginating BS supports IS-801-1 and IS-801-B, and a terminating MS onlysupports IS-801-1. As shown at 1202, the BS may transmitPD_MSG_TYPE=“00000000” and PD_MSG_TYPE=“00000010” to the MS, which mayserve as indication signal(s) specifying that the sender supportsIS-801-1 and IS-801-B, respectively. In response at 1204, the MS maytransmit a PD_MSG_TYPE=“00000000” to the BS, which may serve ascapability signal specifying that the sender supports IS-801-1 and whichmay initiate a position determination communication session, at 1206,using such positioning protocol version.

FIG. 13 shows an example version negotiation process 1300, wherein anoriginating MS only supports IS-801-1, and a terminating BS supportsIS-801-1 and IS-801-B. As shown at 1302, the MS may transmitPD_MSG_TYPE=“00000000” to the BS, which may serve as indicationsignal(s) specifying that the sender supports IS-801-1. In response at1304, the BS may transmit a PD_MSG_TYPE=“00000000” to the MS, which mayserve as capability signal specifying that the sender supports IS-801-1and which may initiate a position determination communication session,at 1306, using such positioning protocol version.

FIG. 14 shows an example version negotiation process 1400, wherein anoriginating BS supports IS-801-1 and IS-801-B, and a terminating MSsupports IS-801-1 and IS-801-A. As shown at 1402, the BS may transmitPD_MSG_TYPE=“00000000” and PD_MSG_TYPE=“00000010” to the MS, which mayserve as indication signal(s) specifying that the sender supportsIS-801-1 and IS-801-B, respectively. In response at 1404, the MS maytransmit a PD_MSG_TYPE=“00000000” to the BS, which may serve ascapability signal specifying that the sender supports IS-801-1 and whichmay initiate a position determination communication session, at 1406,using such positioning protocol version.

FIG. 15 shows an example version negotiation process 1500, wherein anoriginating MS supports IS-801-1 and IS-801-A, and a terminating BSsupports IS-801-1 and IS-801-B. As shown at 1502, the MS may transmitPD_MSG_TYPE=“00000000” and PD_MSG_TYPE=“00000001” to the BS, which mayserve as indication signal(s) specifying that the sender supportsIS-801-1 and IS-801-A, respectively. At 1504, the BS may set aBS_LV_REV=“00000000” despite that the BS supports IS-801-B. Thus, inresponse at 1506, the BS may transmit a PD_MSG_TYPE=“00000000” withBS_LV_REV=“00000000” to the MS, which may serve as capability signalspecifying that the sender supports IS-801-1 and which may initiate aposition determination communication session, at 1508, using suchpositioning protocol version.

FIG. 16 shows an example version negotiation process 1600, wherein anoriginating BS supports IS-801-1 and IS-801-B, and a terminating MSsupports IS-801-1 and IS-801-B. As shown at 1602, the BS may transmitPD_MSG_TYPE=“00000000” and PD_MSG_TYPE=“00000010” to the MS, which mayserve as indication signal(s) specifying that the sender supportsIS-801-1 and IS-801-B, respectively. In response at 1604, the MS maytransmit a PD_MSG_TYPE=“00000010” to the BS, which may serve ascapability signal specifying that the sender supports IS-801-B and whichmay initiate a position determination communication session, at 1606,using such positioning protocol version.

FIG. 17 shows an example version negotiation process 1700, wherein anoriginating MS supports IS-801-1 and IS-801-B, and a terminating BSsupports IS-801-1 and IS-801-B. As shown at 1702, the MS may transmitPD_MSG_TYPE=“00000000” and PD_MSG_TYPE=“00000010” to the BS, which mayserve as indication signal(s) specifying that the sender supportsIS-801-1 and IS-801-B, respectively. In response at 1704, the BS maytransmit a PD_MSG_TYPE=“00000010” to the MS, which may serve ascapability signal specifying that the sender supports IS-801-B and whichmay initiate a position determination communication session, at 1706,using such positioning protocol version.

FIG. 18 shows an example version negotiation process 1800, wherein anoriginating BS supports IS-801-1, IS-801-A and IS-801-B, and aterminating MS supports IS-801-1, IS-801-A and IS-801-B. As shown at1802, the BS may transmit PD_MSG_TYPE=“00000000”,PD_MSG_TYPE=“00000001”, and PD_MSG_TYPE=“00000010” to the MS, which mayserve as indication signal(s) specifying that the sender supportsIS-801-1, IS-801-A, and IS-801-B, respectively. In response at 1804, theMS may transmit a PD_MSG_TYPE=“00000010” to the BS, which may serve ascapability signal specifying that the sender supports IS-801-B and whichmay initiate a position determination communication session, at 1806,using such positioning protocol version.

FIG. 19 shows an example version negotiation process 1900, wherein anoriginating MS supports IS-801-1, IS-801-A and IS-801-B, and aterminating BS supports IS-801-1, IS-801-A and IS-801-B. As shown at1902, the MS may transmit PD_MSG_TYPE=“00000000” andPD_MSG_TYPE=“00000010” to the MS, which may serve as indicationsignal(s) specifying that the sender supports IS-801-1 and IS-801-B,respectively. In response at 1904, the BS may transmit aPD_MSG_TYPE=“00000010” to the MS, which may serve as capability signalspecifying that the sender supports IS-801-B and which may initiate aposition determination communication session, at 1906, using suchpositioning protocol version.

FIG. 20 is an illustrative diagram 2000 illustrating initial portions ofsome example PDDM messages that may provide an indication signal(s) toinitiate and/or otherwise support a position determination process usingone or more positioning protocol versions. Here, for example, message2002 has PD_MSG_TYPE=“00000000” and may be compliant with IS-801-1,message 2004 has PD_MSG_TYPE=“00000001” and may be compliant withIS-801-A, and message 2006 has PD_MSG_TYPE=“00000010” and may becompliant with IS-801-B and/or extendable to be forward compliant withone or more future IS-801 versions and/or the like. Message 2006, forexample, may include message length fields/information, e.g., PD_MSG_LEN(MSB) and PD_MSG_LEN (LSB). Message 2006, for example, may include an apayload encoded, at least in part, using an extensible syntax language,e.g., an Abstract Syntax Notation One (ASN.1), an Extensible MarkupLanguage (XML), and/or the like.

FIG. 21 is an illustrative diagram 2100 illustrating example transportmessage having a plurality of PDDM messages, e.g., as in FIG. 20, whichas shown in this example may be concatenated together and transmitted ina single transport message. The receiving device may decode theIS-801-1, detect the presence of non-expected bits at the end to thefirst PDDM (e.g., the PD_MSG_TYPE=“00000000” PDDM), and decode anyadditional PDDMs (here, e.g., the PD_MSG_TYPE=“00000001” PDDM andPD_MSG_TYPE=“00000010” PDDM). Thus, for example, the PD_MSG_LENfields/information may identify the starting and ending points for thePDDMs. In certain implementations, for example, a device may parsethrough or otherwise process all or portions of such indicationsignal(s), perhaps skipping over some of the data, to identify certainpertinent data.

By way of further example, FIG. 22 is a flow-diagram illustrating anexemplary method 2200 that may be implemented in one or more apparatusesto process a transport message, for example, as in FIG. 21. At block2202, a transport message may be received or otherwise accessed. Atblock 2204, a PD_MSG_TYPE=“00000000” may be identified and associatedPDDM decoded at block 2206. At block 2208, it may be determined whethermore bits (e.g., beyond the end of the PD_MSG_TYPE=“00000000” PDDM) maybe available. If the decision at block 2208 is NO, then at block 2210 itmay be established that the sender is only enabled to support IS-801-1.If the decision at block 2208 is YES, then at block 2212 decoding of theadditional bits may continue to detect a PD_MSG_TYPE associated withanother PDDM. Thus, for example, at block 2214 it may be determinedwhether the PD_MSG_TYPE=“00000001” then at block 2216 (if IS-801-A issupported by the terminating device) the PD_MSG_TYPE=“00000001” may beskipped over and at block 2218 it may be determined whether more bits(e.g., beyond the end of the PD_MSG_TYPE=“00000001” PDDM) are available.

If the decision at block 2218 is NO, then at block 2220 it may beestablished that the sender is enabled to support IS-801-1 and IS-801-A.If the decision at block 2218 is YES, then at block 2222 decoding of theadditional bits may continue to detect a PD_MSG_TYPE associated withanother PDDM. Here, for example a third PDDM may include aPD_MSG_TYPE=“00000010” PDDM, such that at block 2224 it may beestablished that the sender is enabled to support IS-801-1, IS-801-A,and IS-801-B. At block 2222, the third PDDM may be decoded.

With reference back to block 2214, if it is determined that thePD_MSG_TYPE=“00000010” then at block 2226 the IS-801-B PDDM may bedecoded, and at block 2228, it may be established that the sender isenabled to support IS-801-1 and IS-801-B.

Reference is now made to FIG. 23, which is a flow diagram illustratingsome example message exchanges between two devices (e.g., a locationserver and a MS) that may occur as part of a position determinationprocess 2300. Here, for example, position determination process 2300 maybe enabled while initiating and/or following initiation of a positiondetermination communication session established using a thirdpositioning protocol version. By way of example, but not limitation, athird positioning protocol version may be compliant with IS-801-B.

In position determination process 2300, for example, a MS may transmitone or more message(s) 2302 (e.g. PDDMs and/or transport messages) to alocation server to request and/or provide certain positioning relatedinformation/elements. By way of example but not limitation, as part ofIS-801-B message(s) 2302 may include a Request Advanced BS Capabilities,a Request GNSS Acquisition Assistance, an unsolicited Provide PilotPhase Measurement, an unsolicited Provide Advanced MS Information, andan unsolicited Provide Advanced System Parameters Information. Thus, forexample, at this point in position determination process 2300 the MS maymeasure a pilot phases from all visible BS's and send such measurementsto the location server through the Provide Pilot Phase Measurementmessage. Additionally, the MS may send the Provide Advanced MSInformation message (e.g., indicating the MS's desired positioningcapabilities), and optionally, the Provide Advanced System ParametersInformation message. The MS may send the Request Advanced BSCapabilities, and a Request GNSS Acquisition Assistance.

In position determination process 2300, for example, the location servermay transmit one or more message(s) 2304 (e.g. PDDMs and/or transportmessages) to the MS to provide certain positioning relatedinformation/elements. By way of example but not limitation, as part ofIS-801-B message(s) 2304 may include a Provide Advanced BS Capabilitiesmessage and a Provide GNSS Acquisition Assistance message. Thus, forexample, at this point in position determination process 2300, using theprovided pilot phase measurements, the location server may estimates apreliminary position of the MS. This position may be referred to as aprefix. Based on this prefix, the location server may determine one ormore search windows for the visible SVs and may send such information tothe MS via the Provide GNSS Acquisition Assistance message.

Also as shown with position determination process 2300, for example, aMS may transmit one or more message(s) 2306 (e.g. PDDMs and/or transportmessages) to the location server as part of IS-801-B message(s) 2306,such as, a Request GNSS Sensitivity Assistance message. For example, aMS may determine that GNSS Sensitivity Assistance (SA) may be useful indetecting weak signals from a GNSS SV, and as such request such SAinformation from location server. As shown, the location server mayrespond by sending one or more message(s) 2308, such as, a Provide GNSSSensitivity Assistance message to the MS. Thus, for example, the MS maythen attempt to use the GNSS SA information received from the locationserver to continue measuring pseudoranges and possibly re-measuringpilot phases.

As shown with position determination process 2300, for example, a MS maytransmit one or more message(s) 2310 (e.g. PDDMs and/or transportmessages) to the location server as part of IS-801-B message(s) 2310,such as, a Request Advanced Location Response message, an unsolicitedProvide Pilot Phase Measurement message, an unsolicited Provide TimeOffset Measurement message, and an unsolicited Provide GNSS PseudorangeMeasurement message. For example, pseudorange measurement data may besent to the location server through the Provide GNSS PseudorangeMeasurement message. The MS may also provide pilot phase measurementdata from the visible base stations again via the Provide Pilot PhaseMeasurement message. A Provide Time Offset Measurement message may beincluded, for example, if a carrier is 1X. Along with such measurements,a Request Location Response message may be sent to the location server.

As illustrated in this example, the location server may transmit one ormore message(s) 2312 to the MS to provide certain positioning relatedinformation/elements. By way of example but not limitation, as part ofIS-801-B message(s) 2304 may include a Provide Advanced LocationCapabilities message. Thus, for example, at this point in positiondetermination process 2300, using the received measurements frommessages 2310, a final position of the MS may be determined by thelocation server and final position information may be sent to the MS tocomplete the call flow. For example, as illustrated by the response ofthe MS in sending message(s) 2314, the MS may send an unsolicitedProvide Advanced MS Information message that includes a Session End Flagset to terminate the session (e.g., here, Session End Flag=1).

By way of further example, as part of IS-801-B request elements sent bya MS may include one or more of the following: a Request LocationResponse, a Request BS Capabilities, a Request Base Station Almanac, aRequest GPS Acquisition Assistance, Request GPS Sensitivity Assistance,a Request GPS Location Assistance, Request GPS Almanac, a Request GPSEphemeris, a Request GPS Navigation Message Bits, a Request GPS AlmanacCorrection, a Request GPS Satellite Health Information, a RequestExtended Location Response, a Request Extended BS Capabilities, aRequest Enhanced Base Station Almanac, a Request General AcquisitionAssistance, a Request Extended GPS Sensitivity Assistance, a Request GPSAlmanac v1, a Request Extended GPS Ephemeris, a Request Extended GPSNavigation Message Bits, a Request Extended GPS Almanac Correction, aRequest Extended GPS Satellite Health Information, a Request GPS CoarseLocation Assistance, a Request GPS Coarse Acquisition Assistance, aRequest DGPS Assistance, a Request GPS Real-Time Integrity Information,a Request Advanced Location Response, a Request Advanced BSCapabilities, a Request Advanced UMB Base Station Almanac, a RequestAdvanced HRPD Base Station Almanac, a Request Advanced 1X Base StationAlmanac, a Request GNSS Acquisition Assistance, a Request GNSSSensitivity Assistance, a Request Modernized GPS Ephemeris and ClockCorrection, a Request QZSS Ephemeris and Clock Correction, a RequestGLONASS Ephemeris and Clock Correction, a Request Galileo Ephemeris andClock Correction, a Request GEO Navigation Message Parameters, a RequestModernized GPS Almanac, a Request QZSS Almanac, a Request GLONASSAlmanac, a Request Galileo Almanac, a Request GEO Almanacs MessageParameters, a Request GPS Ionospheric Model, a Request GALILEOIonospheric Model, a Request QZSS Ionospheric Model, a Request GNSS-GNSSTime Offset, a Request GPS UTC Model, a Request Advanced GNSS SatelliteHealth Information, and/or a Request DGNSS Assistance.

By way of further example, as part of IS-801-B response elements sent bya MS may include one or more of the following: a Reject, a ProvideLocation Response, Provide MS Information, a Provide AutonomousMeasurement Weighting Factors, a Provide Pseudorange Measurement, aProvide Pilot Phase Measurement, a Provide Time Offset Measurement, aProvide Cancellation Acknowledgement, am Extended Reject, a ProvideExtended Location Response, a Provide Extended MS Information; a ProvideAutonomous Measurement Weighting Factors v1, a Provide General LocationMeasurement, a Provide Extended Cancellation Acknowledgement, a ProvideGPS Coarse Location Response, a Provide Messaging Delay Measurement, aProvide Bearing Measurement, a Provide Serving System Information, anAdvanced Reject, a Provide Advanced Location Response, a ProvideAdvanced MS Information, a Provide UMB Pilot Time Offset Measurement, aProvide HRPD Pilot Phase Measurement, a Provide GNSS PseudorangeMeasurement, a Provide Advanced Cancellation Acknowledgement, and/or aProvide Advanced System Parameters Information.

By way of further example, as part of IS-801-B request elements receivedby a MS may include one or more of the following: a Request LocationResponse, a Request MS Information, a Request Autonomous MeasurementWeighting Factors, a Request Pseudorange Measurement, a Request PilotPhase Measurement, a Request Time Offset Measurement, a RequestCancellation, a Request Extended Location Response, a Request ExtendedMS Information, a Request Autonomous Measurement Weighting Factors v1, aRequest General Location Measurement, a Request Extended Cancellation, aRequest GPS Coarse Location Response, a Request Messaging DelayMeasurement, a Request Bearing Measurement, a Request Serving SystemInformation, a Request Advanced Location Response, a Request Advanced MSInformation, a Request UMB Pilot Time Offset Measurement, a Request HRPDPilot Phase Measurement, a Request GNSS Pseudorange Measurement, aRequest Advanced Cancellation, and/or a Request Advanced SystemParameters Information.

By way of further example, as part of IS-801-B response elementsreceived by a MS may include one or more of the following: a Reject, aProvide Location Response, a Provide BS Capabilities, a Provide BaseStation Almanac, a Provide GPS Acquisition Assistance, a Provide GPSSensitivity Assistance, a Provide GPS Location Assistance—SphericalCoordinates, a Provide GPS Location Assistance—Cartesian Coordinates, aProvide GPS Almanac, a Provide GPS Ephemeris, a Provide GPS NavigationMessage Bits, a Provide GPS Almanac Correction, a Provide GPS SatelliteHealth Information, an Extended Reject, a Provide Extended LocationResponse, a Provide Extended BS Capabilities, a Provide Enhanced BaseStation Almanac, a Provide General Acquisition Assistance, a ProvideExtended GPS Sensitivity Assistance, a Provide GPS Almanac v1, a ProvideExtended GPS Ephemeris, a Provide Extended GPS Navigation Message Bits,a Provide Extended GPS Almanac Correction, a Provide Extended GPSSatellite Health Information, a Provide GPS Coarse Location Assistance,a Provide GPS Coarse Acquisition Assistance, a Provide DGPS Assistance,a Provide GPS Real-Time Integrity Information, an Advanced Reject, aProvide Advanced Location Response, a Provide Advanced BS Capabilities,a Provide Advanced UMB Base Station Almanac, a Provide Advanced HRPDBase Station Almanac, a Provide Advanced 1X Base Station Almanac, aProvide GNSS Acquisition Assistance, a Provide GNSS SensitivityAssistance, a Provide Modernized GPS Ephemeris and Clock Correction, aProvide QZSS Ephemeris and Clock Correction, a Provide GLONASS Ephemerisand Clock Correction, a Provide Galileo Ephemeris and Clock Correction,a Provide GEO Navigation Message Parameters, a Provide Modernized GPSAlmanac, a Provide QZSS Almanac, a Provide GLONASS Almanac, a ProvideGalileo Almanac, a Provide GEO Almanacs Message Parameters, a ProvideGPS Ionospheric Model, a Provide GALILEO Ionospheric Model, a ProvideQZSS Ionospheric Model, a Provide GNSS-GNSS Time Offset, a Provide GPSUTC Model, a Provide Advanced GNSS Satellite Health Information, and/ora Provide DGNSS Assistance.

By way of further example, as part of IS-801-B, a MS may be enabled toperform the following example positioning protocol version negotiationprocedures:

-   -   (1) If the MS initiates a position determination communication        session then the MS may include a PDDM for each positioning        protocol version it supports in the first Data Burst Message or        IP Packet sent to a BS according to the following:        -   (a) In the first PDDM the MS may set the PD_MSG_TYPE field            to ‘00000000’ (e.g., a value indicative of IS-801-1) and may            include a “Request BS Capabilities” request element and a            “Provide MS Information” response element;        -   (b) If MS_LS_REV of type ‘000001’ is supported by the MS            then in the second PDDM the MS may set the PD_MSG_TYPE field            to ‘00000001’ (e.g., a value indicative of IS-801-A) and may            include a “Request Extended BS Capabilities” request element            and a “Provide Extended MS Information” response element;        -   (c) In the last PDDM the MS may set the PD_MSG_TYPE field to            ‘00000010’ (e.g., a value indicative of IS-801-B) and may            include a “Request Advanced BS Capabilities” request element            and a “Provide Advanced MS Information” response element;    -   (2) If the BS initiates a position determination communication        session then the MS may respond using the highest mutually        supported positioning protocol version.    -   (3) Once a positioning protocol version has been negotiated that        protocol version may be used for the duration of the position        determination communication session. Thus, any unexpected        messages may simply be ignored.

By way of further example, as part of IS-801-B request elements sent bya BS and/or the like may include one or more of the following: a RequestLocation Response, a Request MS Information, a Request AutonomousMeasurement Weighting Factors, a Request Pseudorange Measurement, aRequest Pilot Phase Measurement, a Request Time Offset Measurement, aRequest Cancellation, a Request Extended Location Response, a RequestExtended MS Information, a Request Autonomous Measurement WeightingFactors v1, a Request General Location Measurement, a Request ExtendedCancellation, a Request GPS Coarse Location Response, a RequestMessaging Delay Measurement, a Request Bearing Measurement, a RequestServing System Information, a Request Advanced Location Response, aRequest Advanced MS Information, a Request UMB Pilot Time OffsetMeasurement, a Request HRPD Pilot Phase Measurement, a Request GNSSPseudorange Measurement, a Request Advanced Cancellation, and/or aRequest Advanced System Parameters Information.

By way of further example, as part of IS-801-B response elements sent bya BS and/or the like may include one or more of the following: a Reject,a Provide Location Response, a Provide BS Capabilities, a Provide BaseStation Almanac, a Provide GPS Acquisition Assistance, a Provide GPSSensitivity Assistance, a Provide GPS Location Assistance—SphericalCoordinates, a Provide GPS Location Assistance—Cartesian Coordinates, aProvide GPS Almanac, a Provide GPS Ephemeris, a Provide GPS NavigationMessage Bits, a Provide GPS Almanac Correction, a Provide GPS SatelliteHealth Information, an Extended Reject, a Provide Extended LocationResponse, a Provide Extended BS Capabilities, a Provide Enhanced BaseStation Almanac, a Provide General Acquisition Assistance, a ProvideExtended GPS Sensitivity Assistance, a Provide GPS Almanac v1, a ProvideExtended GPS Ephemeris, a Provide Extended GPS Navigation Message Bits,a Provide Extended GPS Almanac Correction, a Provide Extended GPSSatellite Health Information, a Provide GPS Coarse Location Assistance,a Provide GPS Coarse Acquisition Assistance, a Provide DGPS Assistance,a Provide GPS Real-Time Integrity Information, an Advanced Reject, aProvide Advanced Location Response, a Provide Advanced BS Capabilities,a Provide Advanced UMB Base Station Almanac, a Provide Advanced HRPDBase Station Almanac, a Provide Advanced 1X Base Station Almanac, aProvide GNSS Acquisition Assistance, a Provide GNSS SensitivityAssistance, a Provide Modernized GPS Ephemeris and Clock Correction, aProvide QZSS Ephemeris and Clock Correction, a Provide GLONASS Ephemerisand Clock Correction, a Provide Galileo Ephemeris and Clock Correction,a Provide GEO Navigation Message Parameters, a Provide Modernized GPSAlmanac, a Provide QZSS Almanac, a Provide GLONASS Almanac, a ProvideGalileo Almanac, a Provide GEO Almanacs Message Parameters, a ProvideGPS Ionospheric Model, a Provide GALILEO Ionospheric Model, a ProvideQZSS Ionospheric Model, a Provide GNSS-GNSS Time Offset, a Provide GPSUTC Model, a Provide Advanced GNSS Satellite Health Information, and/ora Provide DGNSS Assistance.

By way of further example, as part of IS-801-B request elements receivedby a BS and/or the like may include one or more of the following: aRequest Location Response, a Request BS Capabilities, a Request BaseStation Almanac, a Request GPS Acquisition Assistance, a Request GPSSensitivity Assistance, a Request GPS Location Assistance, a Request GPSAlmanac, a Request GPS Ephemeris, a Request GPS Navigation Message Bits,a Request GPS Almanac Correction, a Request GPS Satellite HealthInformation, a Request Extended Location Response, a Request Extended BSCapabilities, a Request Enhanced Base Station, a Request GeneralAcquisition Assistance, a Request Extended GPS Sensitivity, a RequestGPS Almanac v1, a Request Extended GPS Ephemeris, a Request Extended GPSNavigation Message Bits, a Request Extended GPS Almanac Correction, aRequest Extended GPS Satellite Health Information, a Request GPS CoarseLocation Assistance, a Request GPS Coarse Acquisition Assistance, aRequest DGPS Assistance, a Request GPS Real-Time Integrity Information,a Request Advanced Location Response, a Request Advanced BSCapabilities, a Request Advanced UMB Base Station Almanac, a RequestAdvanced HRPD Base Station Almanac, a Request Advanced 1X Base StationAlmanac, a Request GNSS Acquisition Assistance, a Request GNSSSensitivity Assistance, a Request Modernized GPS Ephemeris and ClockCorrection, a Request QZSS Ephemeris and Clock Correction, a RequestGLONASS Ephemeris and Clock Correction, a Request Galileo Ephemeris andClock Correction, a Request GEO Navigation Message Parameters, a RequestModernized GPS Almanac, a Request QZSS Almanac, a Request GLONASSAlmanac, a Request Galileo Almanac, a Request GEO Almanacs MessageParameters, a Request GPS Ionospheric Mode, a Request GALILEOIonospheric Model, a Request QZSS Ionospheric Model, a Request GNSS-GNSSTime Offset, a Request GPS UTC Model, a Request Advanced GNSS SatelliteHealth Information, and/or a Request DGNSS Assistance.

By way of further example, as part of IS-801-B response elementsreceived by a BS and/or the like may include one or more of thefollowing: a Reject, a Provide Location Response, a Provide MSInformation, a Provide Autonomous Measurement Weighting Factors, aProvide Pseudorange Measurement, a Provide Pilot Phase Measurement, aProvide Time Offset Measurement, a Provide Cancellation Acknowledgement,a Extended Reject, a Provide Extended Location Response, a ProvideExtended MS Information, a Provide Autonomous Measurement WeightingFactors v1, a Provide General Location Measurement, a Provide ExtendedCancellation Acknowledgement, a Provide GPS Coarse Location Response, aProvide Messaging Delay Measurement, a Provide Bearing Measurement, aProvide Serving System Information, an Advanced Reject, a ProvideAdvanced Location Response, a Provide Advanced MS Information, a ProvideUMB Pilot Time Offset Measurement, a Provide HRPD Pilot PhaseMeasurement, a Provide GNSS Pseudorange Measurement, a Provide AdvancedCancellation Acknowledgement, and/or a Provide Advanced SystemParameters Information.

By way of further example, as part of IS-801-B, a BS and/or other likedevice may be enabled to perform the following example positioningprotocol version negotiation procedures:

-   -   (1) If the BS initiates a position determination communication        session, then the BS may include a PDDM for each positioning        protocol version it supports in the first Data Burst Message or        IP Packet sent to a MS according to the following:        -   (a) In the first PDDM the BS may set the PD_MSG_TYPE field            to ‘00000000’ (e.g., a value indicative of IS-801-1) and may            include a “Request MS Information” request element and a            “Provide BS Capabilities” response element;        -   (b) If BS_LS_REV of type ‘00000001’ (e.g., a value            indicative of IS-801-A) is supported by the BS then in the            second PDDM the BS may set the PD_MSG_TYPE field to            ‘00000001’ and may include a “Request Extended MS            Information” request element and a “Provide Extended BS            Capabilities” response element;        -   (c) In the last PDDM the BS may set the PD_MSG_TYPE field to            ‘00000010’ (e.g., a value indicative of IS-801-B) and may            include a “Request Advanced MS Information” request element            and a “Provide Advanced BS Capabilities” response element.    -   (2) If the MS initiates a position determination communication        session then the BS may respond using the highest mutually        supported positioning protocol version.    -   (3) Once a positioning protocol version has been negotiated that        protocol version may be used for the duration of the session.        Any unexpected messages may simply be ignored.

Reference is now made to FIG. 24 which shows another example versionnegotiation process 2400. Here, an originating BS may be enabled tosupport hypothetical future positioning services protocol versions“IS-801-C” and “IS-801-D” and IS-801-1. The MS in this example may beenabled to support “IS-801-C” and IS-801-1. As shown at 2402, the BS maytransmit PD_MSG_TYPE=“00000000”, PD_MSG_TYPE=“00000011” (e.g.,associated with “IS-801-C”) and PD_MSG_TYPE=“00000100” (e.g., associatedwith “IS-801-D”) to the MS concatenated within a transport message,which may serve as indication signal(s) specifying that the sendersupports IS-801-1, “IS-801-C” and “IS-801-D”, respectively. In responseat 2404, the MS may transmit a PD_MSG_TYPE=“00000011” to the MS, whichmay serve as capability signal specifying that the sender supports“IS-801-C” and which may initiate a position determination communicationsession, at 2406, using such positioning protocol version.

Reference is now made to FIG. 25 which shows yet another example versionnegotiation process 2500. Here, an originating BS may be enabled tosupport hypothetical future positioning services protocol versions“IS-801-C”, “IS-801-D” and IS-801-1. The MS in this example may beenabled to support “IS-801-C”, IS-801-B and IS-801-1. As shown at 2502,the BS may transmit PD_MSG_TYPE=“00000000”, and a PD_MSG_TYPE=“00000010”to the MS concatenated within a transport message. Here, for example,the PD_MSG_TYPE=“00000010” is enabled to serve as indication signal(s)specifying that the sender supports certain additional versions such as“IS-801-C” (e.g., as represented by BS_LS_REV=“000011”) and “IS-801-D”(e.g., as represented by BS_LS_REV=“000100”). In response at 2504, theMS may transmit a PD_MSG_TYPE=“00000010” (e.g., with MS_LS_REV=“000010”,“000011”) to the BS, which may serve as capability signal specifyingthat the sender supports IS-801-B and “IS-801-C” and which may initiatea position determination communication session, at 2506, using thehighest mutually supported positioning protocol version, here e.g.,“IS-801-C”.

While some portions of the detailed description have been presented interms of algorithms or symbolic representations of operations on binarydigital signals stored within a memory of a specific apparatus orspecial purpose computing device or platform, in the context of thisparticular specification, the term specific apparatus or the likeincludes a general purpose computer once it is programmed to performparticular functions pursuant to instructions from program software.Algorithmic descriptions or symbolic representations are examples oftechniques used by those of ordinary skill in the signal processing orrelated arts to convey the substance of their work to others skilled inthe art. An algorithm as here, and generally, is considered to be aself-consistent sequence of operations or similar signal processingleading to a desired result. In this context, operations or processinginvolve physical manipulation of physical quantities. Typically,although not necessarily, such quantities may take the form ofelectrical or magnetic signals capable of being stored, transferred,combined, compared or otherwise manipulated. It has proven convenient attimes, principally for reasons of common usage, to refer to such signalsas bits, data, values, elements, symbols, characters, terms, numbers,numerals or the like. It should be understood, however, that all ofthese or similar terms are to be associated with appropriate physicalquantities and are merely convenient labels. Unless specifically statedotherwise, as apparent in this description, terms such as “processing”,“computing”, “calculating”, “enabling”, “identifying”, “detecting”,“obtaining”, “estimating”, “associating”, “receiving”, “transmitting”“acquiring”, “providing”, “storing”, “accessing”, “determining”, or thelike refer to actions or processes of a specific apparatus, such as aspecial purpose computer or a similar special purpose electroniccomputing and/or communication device. In the context of thisspecification, therefore, a special purpose computer or a similarspecial purpose electronic computing device may be capable ofmanipulating or transforming signals, typically represented as physicalelectronic or magnetic quantities within memories, registers, or otherinformation storage devices, transmission devices, or display devices ofthe special purpose computer or similar special purpose electroniccomputing device.

While there has been illustrated and described what are presentlyconsidered to be example features, it will be understood by thoseskilled in the art that various other modifications may be made, andequivalents may be substituted, without departing from claimed subjectmatter. Additionally, many modifications may be made to adapt aparticular situation to the teachings of claimed subject matter withoutdeparting from the central concept described herein.

Therefore, it may be intended that claimed subject matter not be limitedto the particular examples disclosed, but that such claimed subjectmatter may also include all aspects falling within the scope of appendedclaims, and equivalents thereof.

1. A method comprising: with a first device: determining at least one ofa plurality of positioning protocol versions said first device isoperatively enabled to support in addition to a first positioningprotocol version, said plurality of positioning protocol versionscomprising at least a second positioning protocol version and a thirdpositioning protocol version; accessing at least one indication signalidentifying at least one of said plurality of positioning protocolversions and/or said first positioning protocol version that a seconddevice is operatively enabled to support; and in response to said atleast one indication signal, selectively transmitting at least onecapability signal to said second device, wherein: if determined thatboth said first and second devices are operatively enabled to supportsaid third positioning protocol version, then said at least onecapability signal initiates a position determination communicationsession using said third positioning protocol version; otherwise ifdetermined that said first device is not operatively enabled to supportsaid second positioning protocol version and said second device isoperatively enabled to support said second positioning protocol version,then said at least one capability signal initiates said positiondetermination communication session using said first positioningprotocol version; otherwise if determined that said first and seconddevices are operatively enabled to support said second positioningprotocol version, then said at least one capability signal initiatessaid position determination communication session using said secondpositioning protocol version and is transmitted in compliance with saidsecond positioning protocol version.
 2. The method as recited in claim1, further comprising receiving said at least one indication signal fromsaid second device, said indication signal comprising at least onetransport message comprising a Position Determination Data Message(PDDM) for each positioning protocol version that said second devicesupports, and wherein: a first PDDM is provided which comprises amessage type field associated with said first positioning protocolversion, if said second device supports said second positioning protocolversion, then a second PDDM is provided which comprises a message typefield associated with said second positioning protocol version, aRequest Extended first device Capabilities request element, and aProvide Extended second device Capabilities response element, and ifsaid second device supports said third positioning protocol version,then a third PDDM is provided which comprises a message type fieldassociated with said third positioning protocol version, a RequestAdvanced first device Capabilities request element and a ProvideAdvanced second device Capabilities response element.
 3. The method asrecited in claim 2, wherein said first PDDM further comprises at leastone of a Request first device Capabilities request element and/or aProvide second device Capabilities response element.
 4. The method asrecited in claim 2, further comprising message length information withinsaid transport message, said message length information identifying aportion of said transport message associated with at least one of saidsecond PDDM and/or said third PDDM, and wherein said third PDDMcomprises a payload encoded, at least in part, using an extensiblesyntax language.
 5. The method as recited in claim 2, wherein saidmessage type field associated with said third positioning protocolversion is set to a value indicative of IS-801-B.
 6. The method asrecited in claim 2, wherein said second device comprises a mobilestation (MS) and said first device comprises a base station (BS), andsaid Request Advanced first device Capabilities request elementcomprises a Request Advanced BS Capabilities request element and saidProvide Advanced second device Capabilities response element comprises aProvide Advanced MS Capabilities response element.
 7. The method asrecited in claim 2, wherein said second device comprises a base station(BS) and said first device comprises a mobile station (MS), and saidRequest Advanced first device Capabilities request element comprises aRequest Advanced MS Capabilities request element and said ProvideAdvanced second device Capabilities response element comprises a ProvideAdvanced BS Capabilities response element.
 8. The method as recited inclaim 2, wherein said at least one PDDM comprises a revision levelindicator associated with one of either said first, second, or thirdpositioning protocol versions.
 9. The method as recited in claim 1,wherein said position determination communication session using saidthird positioning protocol version allows said first and/or seconddevices to request and/or provide information associated with at leastone of a Global Navigation Satellite Service (GNSS), an Ultra MobileBroadband (UMB) network, a High Rate Packet Data (HRPD) network, and/ora CDMA2000 1X network.
 10. The method as recited in claim 1, whereinsaid position determination communication session using said thirdpositioning protocol version allows said first and/or second devices toreject and/or cancel position determination related processes associatedwith at least one of a Global Navigation Satellite Service (GNSS), anUltra Mobile Broadband (UMB) network, a High Rate Packet Data (HRPD)network, and/or a CDMA2000 1X network.
 11. The method as recited inclaim 1, wherein one of said first or second devices comprise a mobilestation, and the other one of said first or second devices comprises alocation server.
 12. The method as recited in claim 11, wherein saidlocation server comprises at least one of a Position DeterminationEntity (PDE), a Serving Mobile Location Center (SMLC), a Gateway MobileLocation Center (GMLC), a Standalone AGPS SMLC (SAS), and/or a SUPLLocation Platform (SLP).
 13. The method as recited in claim 11, whereinsaid mobile station and said location server are operatively enabled tocommunicate within a CDMA wireless communication network.
 14. The methodas recited in claim 11, wherein said mobile station and said locationserver are operatively enabled to support at least a Third-GenerationPartnership Project 2 (3GPP2) compliant position determination process.15. The method as recited in claim 1, wherein said second and thirdpositioning protocol versions comprise different and subsequentlydeveloped revisions of at least said first positioning protocol version.16. The method as recited in claim 15, wherein said first positioningprotocol version is compliant with IS-801-1, said second positioningprotocol version is compliant with IS-801-A, and said third positioningprotocol version is compliant with IS-801-B.
 17. A method comprising:with a first device: determining at least one of a plurality ofpositioning protocol versions said first device is operatively enabledto support in addition to a first positioning protocol version, saidplurality of positioning protocol versions comprising at least a secondpositioning protocol version, and a third positioning protocol version;and transmitting an indication signal to a second device, saidindication signal comprising a Position Determination Data Message(PDDM) for each positioning protocol version that said first devicesupports, and wherein: a first PDDM is provided which comprises amessage type field associated with said first positioning protocolversion, if said first device supports said second positioning protocolversion, then a second PDDM is provided which comprises a message typefield associated with said second positioning protocol version, aRequest Extended second device Capabilities request element, and aProvide Extended first device Capabilities response element, and/or ifsaid first device supports said third positioning protocol version, thena third PDDM is provided which comprises a message type field associatedwith said third positioning protocol version, a Request Advanced seconddevice Capabilities request element and a Provide Advanced first deviceCapabilities response element.
 18. The method as recited in claim 17,wherein said indication signal comprises at least one transport messagetransmitted within either a Data Burst Message or an IP Packet.
 19. Themethod as recited in claim 17, wherein said first PDDM further comprisesa Request second device Capabilities request element and/or and aProvide first device Capabilities response element.
 20. The method asrecited in claim 17, further comprising concatenating a plurality ofPDDM together within a transport message, and wherein said third PDDMcomprises a payload encoded, at least in part, using an extensiblesyntax language.
 21. The method as recited in claim 20, furthercomprising providing message length information within said transportmessage, said message length information identifying portions of saidtransport message associated with each of said plurality of PDDM withinsaid transport message.
 22. The method as recited in claim 17, whereinsaid message type indicator comprises a message type field associatedwith said third positioning protocol version set to a value indicativeof IS-801-B.
 23. The method as recited in claim 17, wherein said seconddevice comprises a mobile station (MS) and said first device comprises abase station (BS), and said Request Advanced first device Capabilitiesrequest element comprises a Request Advanced BS Capabilities requestelement and said Provide Advanced second device Capabilities responseelement comprises a Provide Advanced MS Capabilities response element.24. The method as recited in claim 17, wherein said second devicecomprises a base station (BS) and said first device comprises a mobilestation (MS), and said Request Advanced first device Capabilitiesrequest element comprises a Request Advanced MS Capabilities requestelement and said Provide Advanced second device Capabilities responseelement comprises a Provide Advanced BS Capabilities response element.25. The method as recited in claim 17, wherein said at least one PDDMcomprises a revision level indicator associated with one of either saidfirst, second, or third positioning protocol versions.
 26. The method asrecited in claim 17, wherein one of said first or second devicescomprise a mobile station, and the other one of said first or seconddevices comprises a location server.
 27. The method as recited in claim26, wherein said location server comprises at least one of a PositionDetermination Entity (PDE), a Serving Mobile Location Center (SMLC), aGateway Mobile Location Center (GMLC), a Standalone AGPS SMLC (SAS),and/or a SUPL Location Platform (SLP).
 28. The method as recited inclaim 26, wherein said mobile station and said base station areoperatively enabled to communicate within a CDMA wireless communicationnetwork.
 29. The method as recited in claim 26, wherein said mobilestation and said base station are operatively enabled to support atleast a Third-Generation Partnership Project 2 (3GPP2) compliantposition determination process.
 30. The method as recited in claim 17,wherein said second and third positioning protocol versions comprisedifferent and subsequently developed revisions of at least said firstpositioning protocol version.
 31. The method as recited in claim 30,wherein said first positioning protocol version is compliant withIS-801-1, said second positioning protocol version is compliant withIS-801-A, and said third positioning protocol version is compliant withIS-801-B.
 32. An apparatus comprising: means for determining at leastone of a plurality of positioning protocol versions a first device isoperatively enabled to support in addition to a first positioningprotocol version, said plurality of positioning protocol versionscomprising at least a second positioning protocol version, and a thirdpositioning protocol version; means for accessing at least oneindication signal identifying at least one of said plurality ofpositioning protocol versions and/or said first positioning protocolversion that a second device is operatively enabled to support; andmeans for selectively transmitting at least one capability signal tosaid second device in response to said at least one indication signal,wherein: if determined that both said first and second devices areoperatively enabled to support said third positioning protocol version,then said at least one capability signal initiates a positiondetermination communication session using said third positioningprotocol version; otherwise if determined that said first device is notoperatively enabled to support said second positioning protocol versionand said second device is operatively enabled to support said secondpositioning protocol version, then said at least one capability signalinitiates said position determination communication session using saidfirst positioning protocol version; otherwise if determined that saidfirst and second devices are operatively enabled to support said secondpositioning protocol version, then said at least one capability signalinitiates said position determination communication session using saidsecond positioning protocol version and is transmitted in compliancewith said second positioning protocol version.
 33. The apparatus asrecited in claim 32, further comprising: means for receiving said atleast one indication signal from said second device said indicationsignal comprising at least one transport message comprising a PositionDetermination Data Message (PDDM) for each positioning protocol versionthat said second device supports, and wherein: a first PDDM is providedwhich comprises a message type field associated with said firstpositioning protocol version, if said second device supports said secondpositioning protocol version, then a second PDDM is provided whichcomprises a message type field associated with said second positioningprotocol version, a Request Extended first device Capabilities requestelement, and a Provide Extended second device Capabilities responseelement, and if said second device supports said third positioningprotocol version, then a third PDDM is provided which comprises amessage type field associated with said third positioning protocolversion, a Request Advanced first device Capabilities request elementand a Provide Advanced second device Capabilities response element. 34.The apparatus as recited in claim 33, wherein said first PDDM furthercomprises at least one of a Request first device Capabilities requestelement and/or a Provide second device Capabilities response element.35. The apparatus as recited in claim 33, further comprising messagelength information within said transport message, said message lengthinformation identifying a portion of said transport message associatedwith at least one of said second PDDM and/or said third PDDM, andwherein said third PDDM comprises a payload encoded, at least in part,using an extensible syntax language.
 36. The apparatus as recited inclaim 33, wherein said message type field associated with said thirdpositioning protocol version is set to a value indicative of IS-801-B.37. The apparatus as recited in claim 33, wherein said second devicecomprises a mobile station (MS) and said first device comprises a basestation (BS), and said Request Advanced first device Capabilitiesrequest element comprises a Request Advanced BS Capabilities requestelement and said Provide Advanced second device Capabilities responseelement comprises a Provide Advanced MS Capabilities response element.38. The apparatus as recited in claim 33, wherein said second devicecomprises a base station (BS) and said first device comprises a mobilestation (MS), and said Request Advanced first device Capabilitiesrequest element comprises a Request Advanced MS Capabilities requestelement and said Provide Advanced second device Capabilities responseelement comprises a Provide Advanced BS Capabilities response element.39. The apparatus as recited in claim 33, wherein said at least one PDDMcomprises a revision level indicator associated with one of either saidfirst, second, or third positioning protocol versions.
 40. The apparatusas recited in claim 33, wherein said position determinationcommunication session using said third positioning protocol versionallows said first and/or second devices to request and/or provideinformation associated with at least one of a Global NavigationSatellite Service (GNSS), an Ultra Mobile Broadband (UMB) network, aHigh Rate Packet Data (HRPD) network, and/or a CDMA2000 1X network. 41.The apparatus as recited in claim 33, wherein said positiondetermination communication session using said third positioningprotocol version allows said first and/or second devices to rejectand/or cancel position determination related processes associated withat least one of a Global Navigation Satellite Service (GNSS), an UltraMobile Broadband (UMB) network, a High Rate Packet Data (HRPD) network,and/or a CDMA2000 1X network.
 42. The apparatus as recited in claim 32,wherein one of said first or second devices comprise a mobile station,and the other one of said first or second devices comprises a locationserver.
 43. The apparatus as recited in claim 42, wherein locationserver comprises at least one of a Position Determination Entity (PDE),a Serving Mobile Location Center (SMLC), a Gateway Mobile LocationCenter (GMLC), a Standalone AGPS SMLC (SAS), and/or a SUPL LocationPlatform (SLP).
 44. The apparatus as recited in claim 42, wherein saidmobile station and said location server are operatively enabled tocommunicate within a CDMA wireless communication network.
 45. Theapparatus as recited in claim 42, wherein said mobile station and saidlocation server are operatively enabled to support at least aThird-Generation Partnership Project 2 (3GPP2) compliant positiondetermination process.
 46. The apparatus as recited in claim 32, whereinsaid second and third positioning protocol versions comprise differentand subsequently developed revisions of at least said first positioningprotocol version.
 47. The apparatus as recited in claim 46, wherein saidfirst positioning protocol version is compliant with IS-801-1, saidsecond positioning protocol version is compliant with IS-801-A, and saidthird positioning protocol version is compliant with IS-801-B.
 48. Anapparatus comprising: means for determining at least one of a pluralityof positioning protocol versions a first device is operatively enabledto support in addition to a first positioning protocol version, saidplurality of positioning protocol versions comprising at least a secondpositioning protocol version, and a third positioning protocol version;and means for transmitting an indication signal to a second device, saidindication signal comprising a Position Determination Data Message(PDDM) for each positioning protocol version that said first devicesupports, and wherein: a first PDDM is provided which comprises amessage type field associated with said first positioning protocolversion, if said first device supports said second positioning protocolversion, then a second PDDM is provided which comprises a message typefield associated with said second positioning protocol version, aRequest Extended second device Capabilities request element, and aProvide Extended first device Capabilities response element, and/or ifsaid first device supports said third positioning protocol version, thena third PDDM is provided which comprises a message type field associatedwith said third positioning protocol version, a Request Advanced seconddevice Capabilities request element and a Provide Advanced first deviceCapabilities response element.
 49. The apparatus as recited in claim 48,wherein said indication signal comprises at least one transport messagetransmitted within either a Data Burst Message or an IP Packet.
 50. Theapparatus as recited in claim 48, wherein said first PDDM furthercomprises a Request second device Capabilities request element and/orand a Provide first device Capabilities response element.
 51. Theapparatus as recited in claim 48, further comprising; means forconcatenating a plurality of PDDM together within a transport message,and wherein said third PDDM comprises a payload encoded, at least inpart, using an extensible syntax language.
 52. The apparatus as recitedin claim 49, further comprising: means for providing message lengthinformation within said transport message, said message lengthinformation identifying portions of said transport message associatedwith each of said plurality of PDDM within said transport message. 53.The apparatus as recited in claim 48, wherein said message typeindicator comprises a message type field associated with said thirdpositioning protocol version set to a value indicative of IS-801-B. 54.The apparatus as recited in claim 48, wherein said second devicecomprises a mobile station (MS) and said first device comprises a basestation (BS), and said Request Advanced first device Capabilitiesrequest element comprises a Request Advanced BS Capabilities requestelement and said Provide Advanced second device Capabilities responseelement comprises a Provide Advanced MS Capabilities response element.55. The apparatus as recited in claim 48, wherein said second devicecomprises a base station (BS) and said first device comprises a mobilestation (MS), and said Request Advanced first device Capabilitiesrequest element comprises a Request Advanced MS Capabilities requestelement and said Provide Advanced second device Capabilities responseelement comprises a Provide Advanced BS Capabilities response element.56. The apparatus as recited in claim 48, wherein said at least one PDDMcomprises a revision level indicator associated with one of either saidfirst, second, or third positioning protocol versions.
 57. The apparatusas recited in claim 48, wherein one of said first or second devicescomprise a mobile station, and the other one of said first or seconddevices comprises a location server.
 58. The apparatus as recited inclaim 57, wherein said location server comprises at least one of aPosition Determination Entity (PDE), a Serving Mobile Location Center(SMLC), a Gateway Mobile Location Center (GMLC), a Standalone AGPS SMLC(SAS), and/or a SUPL Location Platform (SLP).
 59. The apparatus asrecited in claim 57, wherein said mobile station and said locationserver are operatively enabled to communicate within a CDMA wirelesscommunication network.
 60. The apparatus as recited in claim 57, whereinsaid mobile station and said location server are operatively enabled tosupport at least a Third-Generation Partnership Project 2 (3GPP2)compliant position determination process.
 61. The apparatus as recitedin claim 48, wherein said second and third positioning protocol versionscomprise different and subsequently developed revisions of at least saidfirst positioning protocol version.
 62. The apparatus as recited inclaim 61, wherein said first positioning protocol version is compliantwith IS-801-1, said second positioning protocol version is compliantwith IS-801-A, and said third positioning protocol version is compliantwith IS-801-B.
 63. An apparatus comprising: a transmitter; memorycomprising instructions and/or information operatively associated with aplurality of positioning protocol versions that a first device isoperatively enabled to support in addition to a first positioningprotocol version, said plurality of positioning protocol versionscomprising at least a second positioning protocol version, and a thirdpositioning protocol version; and at least one processing unitoperatively coupled to said transmitter and said memory and operativelyenabled to: access at least one indication signal identifying at leastone of said plurality of positioning protocol versions and/or said firstpositioning protocol version that a second device is operatively enabledto support; and selectively initiate transmission of at least onecapability signal using said transmitter to said second device inresponse to said at least one indication signal, wherein: if determinedthat both said first and second devices are operatively enabled tosupport said third positioning protocol version, then said at least onecapability signal initiates a position determination communicationsession using said third positioning protocol version; otherwise ifdetermined that said first device is not operatively enabled to supportsaid second positioning protocol version and said second device isoperatively enabled to support said second positioning protocol version,then said at least one capability signal initiates said positiondetermination communication session using said first positioningprotocol version; otherwise if determined that said first and seconddevices are operatively enabled to support said second positioningprotocol version, then said at least one capability signal initiatessaid position determination communication session using said secondpositioning protocol version and is transmitted in compliance with saidsecond positioning protocol version.
 64. The apparatus as recited inclaim 63, further comprising: a receiver operatively coupled to said atleast one of said at least one processing unit and/or said memory andoperatively enabled to receive said at least one indication signal fromsaid second device, said indication signal comprising at least onetransport message comprising a Position Determination Data Message(PDDM) for each positioning protocol version that said second devicesupports, and wherein: a first PDDM is provided which comprises amessage type field associated with said first positioning protocolversion, if said second device supports said second positioning protocolversion, then a second PDDM is provided which comprises a message typefield associated with said second positioning protocol version, aRequest Extended first device Capabilities request element, and aProvide Extended second device Capabilities response element, and ifsaid second device supports said third positioning protocol version,then a third PDDM is provided which comprises a message type fieldassociated with said third positioning protocol version, a RequestAdvanced first device Capabilities request element and a ProvideAdvanced second device Capabilities response element.
 65. The apparatusas recited in claim 64, wherein said first PDDM further comprises atleast one of a Request first device Capabilities request element and/ora Provide second device Capabilities response element.
 66. The apparatusas recited in claim 64, further comprising message length informationwithin said transport message, said message length informationidentifying a portion of said transport message associated with at leastone of said second PDDM and/or said third PDDM, and wherein said thirdPDDM comprises a payload encoded, at least in part, using an extensiblesyntax language.
 67. The apparatus as recited in claim 64, wherein saidmessage type field associated with said third positioning protocolversion is set to a value indicative of IS-801-B.
 68. The apparatus asrecited in claim 64, wherein said second device comprises a mobilestation (MS) and said first device comprises a base station (BS), andsaid Request Advanced first device Capabilities request elementcomprises a Request Advanced BS Capabilities request element and saidProvide Advanced second device Capabilities response element comprises aProvide Advanced MS Capabilities response element.
 69. The apparatus asrecited in claim 64, wherein said second device comprises a base station(BS) and said first device comprises a mobile station (MS), and saidRequest Advanced first device Capabilities request element comprises aRequest Advanced MS Capabilities request element and said ProvideAdvanced second device Capabilities response element comprises a ProvideAdvanced BS Capabilities response element.
 70. The apparatus as recitedin claim 64, wherein said at least one PDDM comprises a revision levelindicator associated with one of either said first, second, or thirdpositioning protocol versions.
 71. The apparatus as recited in claim 64,wherein said position determination communication session using saidthird positioning protocol version allows said first and/or seconddevices to request and/or provide information associated with at leastone of a Global Navigation Satellite Service (GNSS), an Ultra MobileBroadband (UMB) network, a High Rate Packet Data (HRPD) network, and/ora CDMA2000 1X network.
 72. The apparatus as recited in claim 64, whereinsaid position determination communication session using said thirdpositioning protocol version allows said first and/or second devices toreject and/or cancel position determination related processes associatedwith at least one of a Global Navigation Satellite Service (GNSS), anUltra Mobile Broadband (UMB) network, a High Rate Packet Data (HRPD)network, and/or a CDMA2000 1X network.
 73. The apparatus as recited inclaim 63, wherein one of said first or second devices comprise a mobilestation, and the other one of said first or second devices comprises alocation server.
 74. The apparatus as recited in claim 73, wherein saidlocation server comprises at least one of a Position DeterminationEntity (PDE), a Serving Mobile Location Center (SMLC), a Gateway MobileLocation Center (GMLC), a Standalone AGPS SMLC (SAS), and/or a SUPLLocation Platform (SLP).
 75. The apparatus as recited in claim 73,wherein said mobile station and said location server are operativelyenabled to communicate within a CDMA wireless communication network. 76.The apparatus as recited in claim 73, wherein said mobile station andsaid location server are operatively enabled to support at least aThird-Generation Partnership Project 2 (3GPP2) compliant positiondetermination process.
 77. The apparatus as recited in claim 63, whereinsaid second and third positioning protocol versions comprise differentand subsequently developed revisions of at least said first positioningprotocol version.
 78. The apparatus as recited in claim 77, wherein saidfirst positioning protocol version is compliant with IS-801-1, saidsecond positioning protocol version is compliant with IS-801-A, and saidthird positioning protocol version is compliant with IS-801-B.
 79. Anapparatus comprising: a transmitter; memory comprising instructionsand/or information operatively associated with a plurality ofpositioning protocol versions that a first device is operatively enabledto support in addition to a first positioning protocol version, saidplurality of positioning protocol versions comprising at least a secondpositioning protocol version, and a third positioning protocol version;and at least one processing unit operatively coupled to said transmitterand said memory and operatively enabled to: initiate transmission of anindication signal to a second device using said transmitter, saidindication signal comprising a Position Determination Data Message(PDDM) for each positioning protocol version that said first devicesupports, and wherein: a first PDDM is provided which comprises amessage type field associated with said first positioning protocolversion, if said first device supports said second positioning protocolversion, then a second PDDM is provided which comprises a message typefield associated with said second positioning protocol version, aRequest Extended second device Capabilities request element, and aProvide Extended first device Capabilities response element, and/or ifsaid first device supports said third positioning protocol version, thena third PDDM is provided which comprises a message type field associatedwith said third positioning protocol version, a Request Advanced seconddevice Capabilities request element and a Provide Advanced first deviceCapabilities response element.
 80. The apparatus as recited in claim 79,wherein said indication signal comprises at least one transport messagetransmitted within either a Data Burst Message or an IP Packet.
 81. Theapparatus as recited in claim 79, wherein said first PDDM furthercomprises a Request second device Capabilities request element and/orand a Provide first device Capabilities response element.
 82. Theapparatus as recited in claim 79, wherein said at least one processingunit is operatively enabled to concatenate a plurality of PDDM togetherwithin a transport message, and said third PDDM comprises a payloadencoded, at least in part, using an extensible syntax language.
 83. Theapparatus as recited in claim 82, wherein said at least one processingunit is operatively enabled to provide message length information withinsaid transport message, said message length information identifyingportions of said transport message associated with each of saidplurality of PDDM within said transport message.
 84. The apparatus asrecited in claim 79, wherein said message type indicator comprises amessage type field associated with said third positioning protocolversion set to a value indicative of IS-801-B.
 85. The apparatus asrecited in claim 79, wherein said second device comprises a mobilestation (MS) and said first device comprises a base station (BS), andsaid Request Advanced first device Capabilities request elementcomprises a Request Advanced BS Capabilities request element and saidProvide Advanced second device Capabilities response element comprises aProvide Advanced MS Capabilities response element.
 86. The apparatus asrecited in claim 79, wherein said second device comprises a base station(BS) and said first device comprises a mobile station (MS), and saidRequest Advanced first device Capabilities request element comprises aRequest Advanced MS Capabilities request element and said ProvideAdvanced second device Capabilities response element comprises a ProvideAdvanced BS Capabilities response element.
 87. The apparatus as recitedin claim 79, wherein said at least one PDDM comprises a revision levelindicator associated with one of either said first, second, or thirdpositioning protocol versions.
 88. The apparatus as recited in claim 79,wherein one of said first or second devices comprise a mobile station,and the other one of said first or second devices comprises a locationserver.
 89. The apparatus as recited in claim 88, wherein said locationserver comprises at least one of a Position Determination Entity (PDE),a Serving Mobile Location Center (SMLC), a Gateway Mobile LocationCenter (GMLC), a Standalone AGPS SMLC (SAS), and/or a SUPL LocationPlatform (SLP).
 90. The apparatus as recited in claim 88, wherein saidmobile station and said location server are operatively enabled tocommunicate within a CDMA wireless communication network.
 91. Theapparatus as recited in claim 88, wherein said mobile station and saidlocation server are operatively enabled to support at least aThird-Generation Partnership Project 2 (3GPP2) compliant positiondetermination process.
 92. The apparatus as recited in claim 79, whereinsaid second and third positioning protocol versions comprise differentand subsequently developed revisions of at least said first positioningprotocol version.
 93. The apparatus as recited in claim 92, wherein saidfirst positioning protocol version is compliant with IS-801-1, saidsecond positioning protocol version is compliant with IS-801-A, and saidthird positioning protocol version is compliant with IS-801-B.
 94. Anarticle comprising: a computer readable medium having computerimplementable instructions stored thereon which if implemented by one ormore processing units in a special-purpose first device operativelyenable the first device to: determine at least one of a plurality ofpositioning protocol versions a first device is operatively enabled tosupport in addition to a first positioning protocol version, saidplurality of positioning protocol versions comprising at least a secondpositioning protocol version, and a third positioning protocol version;access at least one indication signal identifying at least one of saidplurality of positioning protocol versions and/or said first positioningprotocol version that a second device is operatively enabled to support;and selectively initiate transmission of at least one capability signalto said second device in response to said at least one indicationsignal, wherein: if determined that both said first and second devicesare operatively enabled to support said third positioning protocolversion, then said at least one capability signal initiates a positiondetermination communication session using said third positioningprotocol version; otherwise if determined that said first device is notoperatively enabled to support said second positioning protocol versionand said second device is operatively enabled to support said secondpositioning protocol version, then said at least one capability signalinitiates said position determination communication session using saidfirst positioning protocol version; otherwise if determined that saidfirst and second devices are operatively enabled to support said secondpositioning protocol version, then said at least one capability signalinitiates said position determination communication session using saidsecond positioning protocol version and is transmitted in compliancewith said second positioning protocol version.
 95. The article asrecited in claim 94, further comprising computer implementableinstructions which if implemented by the one or more processing unitsoperatively enable the first device to: receive said at least oneindication signal from said second device, said indication signalcomprising at least one transport message comprising a PositionDetermination Data Message (PDDM) for each positioning protocol versionthat said second device supports, and wherein: a first PDDM is providedwhich comprises a message type field associated with said firstpositioning protocol version, if said second device supports said secondpositioning protocol version, then a second PDDM is provided whichcomprises a message type field associated with said second positioningprotocol version, a Request Extended first device Capabilities requestelement, and a Provide Extended second device Capabilities responseelement, and if said second device supports said third positioningprotocol version, then a third PDDM is provided which comprises amessage type field associated with said third positioning protocolversion, a Request Advanced first device Capabilities request elementand a Provide Advanced second device Capabilities response element. 96.The article as recited in claim 95, wherein said first PDDM furthercomprises at least one of a Request first device Capabilities requestelement and/or a Provide second device Capabilities response element.97. The article as recited in claim 95, further comprising messagelength information within said transport message, said message lengthinformation identifying a portion of said transport message associatedwith at least one of said second PDDM and/or said third PDDM, andwherein said third PDDM comprises a payload encoded, at least in part,using an extensible syntax language.
 98. The article as recited in claim95, wherein said message type field associated with said thirdpositioning protocol version is set to a value indicative of IS-801-B.99. The article as recited in claim 95, wherein said second devicecomprises a mobile station (MS) and said first device comprises a basestation (BS), and said Request Advanced first device Capabilitiesrequest element comprises a Request Advanced BS Capabilities requestelement and said Provide Advanced second device Capabilities responseelement comprises a Provide Advanced MS Capabilities response element.100. The article as recited in claim 95, wherein said second devicecomprises a base station (BS) and said first device comprises a mobilestation (MS), and said Request Advanced first device Capabilitiesrequest element comprises a Request Advanced MS Capabilities requestelement and said Provide Advanced second device Capabilities responseelement comprises a Provide Advanced BS Capabilities response element.101. The article as recited in claim 95, wherein said at least one PDDMcomprises a revision level indicator associated with one of either saidfirst, second, or third positioning protocol versions.
 102. The articleas recited in claim 95, wherein said position determinationcommunication session using said third positioning protocol versionallows said first and/or second devices to request and/or provideinformation associated with at least one of a Global NavigationSatellite Service (GNSS), an Ultra Mobile Broadband (UMB) network, aHigh Rate Packet Data (HRPD) network, and/or a CDMA2000 1X network. 103.The article as recited in claim 95, wherein said position determinationcommunication session using said third positioning protocol versionallows said first and/or second devices to reject and/or cancel positiondetermination related processes associated with at least one of a GlobalNavigation Satellite Service (GNSS), an Ultra Mobile Broadband (UMB)network, a High Rate Packet Data (HRPD) network, and/or a CDMA2000 1Xnetwork.
 104. The article as recited in claim 94, wherein one of saidfirst or second devices comprise a mobile station, and the other one ofsaid first or second devices comprises a location server.
 105. Thearticle as recited in claim 104, wherein said location server comprisesat least one of a Position Determination Entity (PDE), a Serving MobileLocation Center (SMLC), a Gateway Mobile Location Center (GMLC), aStandalone AGPS SMLC (SAS), and/or a SUPL Location Platform (SLP). 106.The article as recited in claim 104, wherein said mobile station andsaid location server are operatively enabled to communicate within aCDMA wireless communication network.
 107. The article as recited inclaim 104, wherein said mobile station and said location server areoperatively enabled to support at least a Third-Generation PartnershipProject 2 (3GPP2) compliant position determination process.
 108. Thearticle as recited in claim 94, wherein said second and thirdpositioning protocol versions comprise different and subsequentlydeveloped revisions of at least said first positioning protocol version.109. The article as recited in claim 108, wherein said first positioningprotocol version is compliant with IS-801-1, said second positioningprotocol version is compliant with IS-801-A, and said third positioningprotocol version is compliant with IS-801-B.
 110. An article comprising:a computer readable medium having computer implementable instructionsstored thereon which if implemented by one or more processing units in aspecial-purpose first device operatively enable the first device to:determine at least one of a plurality of positioning protocol versions afirst device is operatively enabled to support in addition to a firstpositioning protocol version, said plurality of positioning protocolversions comprising at least a second positioning protocol version, anda third positioning protocol version; and initiate transmission of anindication signal to a second device, said indication signal comprisinga Position Determination Data Message (PDDM) for each positioningprotocol version that said first device supports, and wherein: a firstPDDM is provided which comprises a message type field associated withsaid first positioning protocol version, if said first device supportssaid second positioning protocol version, then a second PDDM is providedwhich comprises a message type field associated with said secondpositioning protocol version, a Request Extended second deviceCapabilities request element, and a Provide Extended first deviceCapabilities response element, and/or if said first device supports saidthird positioning protocol version, then a third PDDM is provided whichcomprises a message type field associated with said third positioningprotocol version, a Request Advanced second device Capabilities requestelement and a Provide Advanced first device Capabilities responseelement.
 111. The article as recited in claim 110, wherein saidindication signal comprises at least one transport message transmittedwithin either a Data Burst Message or an IP Packet.
 112. The article asrecited in claim 110, wherein said first PDDM further comprises aRequest second device Capabilities request element and/or and a Providefirst device Capabilities response element.
 113. The article as recitedin claim 110, further comprising computer implementable instructionswhich if implemented by the one or more processing units operativelyenable the first device to; concatenate a plurality of PDDM togetherwithin a transport message, and wherein said third PDDM comprises apayload encoded, at least in part, using an extensible syntax language.114. The article as recited in claim 113, further comprising computerimplementable instructions which if implemented by the one or moreprocessing units operatively enable the first device to: provide messagelength information within said transport message, said message lengthinformation identifying portions of said transport message associatedwith each of said plurality of PDDM within said transport message. 115.The article as recited in claim 110, wherein said message type indicatorcomprises a message type field associated with said third positioningprotocol version set to a value indicative of IS-801-B.
 116. The articleas recited in claim 110, wherein said second device comprises a mobilestation (MS) and said first device comprises a base station (BS), andsaid Request Advanced first device Capabilities request elementcomprises a Request Advanced BS Capabilities request element and saidProvide Advanced second device Capabilities response element comprises aProvide Advanced MS Capabilities response element.
 117. The article asrecited in claim 110, wherein said second device comprises a basestation (BS) and said first device comprises a mobile station (MS), andsaid Request Advanced first device Capabilities request elementcomprises a Request Advanced MS Capabilities request element and saidProvide Advanced second device Capabilities response element comprises aProvide Advanced BS Capabilities response element.
 118. The article asrecited in claim 110, wherein said at least one PDDM comprises arevision level indicator associated with one of either said first,second, or third positioning protocol versions.
 119. The article asrecited in claim 110, wherein one of said first or second devicescomprise a mobile station, and the other one of said first or seconddevices comprises a location server.
 120. The article as recited inclaim 119, wherein said location server comprises at least one of aPosition Determination Entity (PDE), a Serving Mobile Location Center(SMLC), a Gateway Mobile Location Center (GMLC), a Standalone AGPS SMLC(SAS), and/or a SUPL Location Platform (SLP).
 121. The article asrecited in claim 119, wherein said mobile station and said locationserver are operatively enabled to communicate within a CDMA wirelesscommunication network.
 122. The article as recited in claim 119, whereinsaid mobile station and said location server are operatively enabled tosupport at least a Third-Generation Partnership Project 2 (3GPP2)compliant position determination process.
 123. The article as recited inclaim 110, wherein said second and third positioning protocol versionscomprise different and subsequently developed revisions of at least saidfirst positioning protocol version.
 124. The article as recited in claim123, wherein said first positioning protocol version is compliant withIS-801-1, said second positioning protocol version is compliant withIS-801-A, and said third positioning protocol version is compliant withIS-801-B.